profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/christianbertschy/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Christian Bertschy christianbertschy Divio AG Zürich, Switzerland http://www.divio.ch

KristianOellegaard/python-nagios-frontend 17

Balbec is a visualization addon for nagios. It displays host and service info either in html for the enduser or in xml for further processing.

christianbertschy/django-shop 2

A Django based shop system

christianbertschy/cmsplugin-disqus 1

Disqus plugin for django CMS

christianbertschy/compass 1

Compass is a Stylesheet Authoring Environment that makes your website design simpler to implement and easier to maintain.

christianbertschy/django-cms-2.0 1

An Advanced Django Cms

christianbertschy/django-cms-toolbar 1

new new django toolbar for 2.4

christianbertschy/django-facebook-graph 1

Toolset of modules to use with facebook graph

christianbertschy/django-debug-toolbar 0

A configurable set of panels that display various debug information about the current request/response.

christianbertschy/django-jquery-file-upload 0

A minimal django project containing a minimal app with a working jquery file upload form based on the work by Sebastian Tschan: http://aquantum-demo.appspot.com/file-upload

pull request commentdjango-cms/django-cms

adding django CMS release script (will be used starting 3.9.0 release)

@FinalAngel @NicolaiRidani for visibility (I'll merge this before starting 3.9 as this is the actual process used to create the release :) )

This file may change during the release cycle (debugging/improvement as I use it), but that's fine as it is standalone.

goutnet

comment created time in 6 hours

PR opened django-cms/django-cms

adding django CMS release script (will be used starting 3.9.0 release)

Description

This PR adds an script to automate the release process. This will be used for 3.9.0 and onward (will auto-merge this before starting the actual release cycle)

Checklist

  • [x ] I have opened this pull request against develop
  • [x] I have updated the CHANGELOG.rst
  • [x] I have added or modified the tests when changing logic
  • [x] I have read the contribution guidelines and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.
+349 -0

0 comment

2 changed files

pr created time in 6 hours

issue openeddocker/compose

docker-compose up doesnt work

Description of the issue

Context information (for bug reports)

Output of docker-compose version

docker-compose version 1.29.1, build c34c88b2
docker-py version: 5.0.0
CPython version: 3.9.0
OpenSSL version: OpenSSL 1.1.1g  21 Apr 2020

Output of docker version

Client:
 Cloud integration: 1.0.14
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.16.3
 Git commit:        370c289
 Built:             Fri Apr  9 22:49:36 2021
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8728dd2
  Built:            Fri Apr  9 22:44:56 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker-compose config (Make sure to add the relevant -f and other flags)

services:
  db:
    environment:
      POSTGRES_DB: postgres
      POSTGRES_PASSWORD: postgres
      POSTGRES_USER: postgres
    image: postgres
    volumes:
    - C:\Users\docker\Desktop\gp_turnieje_backend\data\db:/var/lib/postgresql/data:rw
  redis:
    command: redis-server
    container_name: rd01
    image: redis:latest
    restart: always
    volumes:
    - redisdata:/data:rw
  web:
    build:
      context: C:\Users\docker\Desktop\gp_turnieje_backend
    command: sh -c "python3 manage.py migrate && gunicorn gp_turnieje_backend.wsgi:application
      --bind 0.0.0.0:8000 --workers 4 -k gevent --worker-connections 100 --config
      config/gunicorn_config.py"
    depends_on:
      db:
        condition: service_started
      redis:
        condition: service_started
    environment:
      DJANGO_ENV: production
    ports:
    - published: 8000
      target: 8000
    volumes:
    - C:\Users\docker\Desktop\gp_turnieje_backend\log\gp_games:/log/gp_games/:rw
version: '3.9'
volumes:
  redisdata: {}

Steps to reproduce the issue

1.Use docker-compose

Observed result

Stacktrace / full error message

C:\Users\docker\Desktop\gp_turnieje_backend>docker-compose version
docker-compose version 1.29.1, build c34c88b2
docker-py version: 5.0.0
CPython version: 3.9.0
OpenSSL version: OpenSSL 1.1.1g  21 Apr 2020

C:\Users\docker\Desktop\gp_turnieje_backend>docker-compose up --build
Docker Compose is now in the Docker CLI, try `docker compose up`

Pulling redis (redis:latest)...
Traceback (most recent call last):
  File "docker\credentials\store.py", line 79, in _execute
  File "subprocess.py", line 420, in check_output
  File "subprocess.py", line 524, in run
subprocess.CalledProcessError: Command '['C:\\Program Files\\Docker\\Docker\\resources\\bin\\docker-credential-desktop.EXE', 'get']' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "docker\auth.py", line 264, in _resolve_authconfig_credstore
  File "docker\credentials\store.py", line 35, in get
  File "docker\credentials\store.py", line 93, in _execute
docker.credentials.errors.StoreError: Credentials store docker-credential-desktop exited with "error getting credentials - err: exit status 1, out: `Nie można odnaleźć elementu.`".

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "docker-compose", line 3, in <module>
  File "compose\cli\main.py", line 81, in main
  File "compose\cli\main.py", line 203, in perform_command
  File "compose\metrics\decorator.py", line 18, in wrapper
  File "compose\cli\main.py", line 1189, in up
  File "compose\cli\main.py", line 1169, in up
  File "compose\project.py", line 664, in up
  File "compose\service.py", line 358, in ensure_image_exists
  File "compose\service.py", line 1251, in pull
  File "compose\progress_stream.py", line 99, in get_digest_from_pull
  File "compose\service.py", line 1218, in _do_pull
  File "docker\api\image.py", line 411, in pull
  File "docker\auth.py", line 47, in get_config_header
  File "docker\auth.py", line 324, in resolve_authconfig
  File "docker\auth.py", line 235, in resolve_authconfig
  File "docker\auth.py", line 280, in _resolve_authconfig_credstore
docker.errors.DockerException: Credentials store error: StoreError('Credentials store docker-credential-desktop exited with "error getting credentials - err: exit status 1, out: `Nie można odnaleźć elementu.`".')
[8792] Failed to execute script docker-compose






Additional information

Windows 10 PRO 20H2 19042.928

created time in 10 hours

issue commentdocker/compose

docker-compose cant mount a source volume thats an encfs volume

same behaviour with gocryptfs

I might got arround this behaviour with the option "-allow_other". Details can be found here for this flag. https://github.com/rfjakob/gocryptfs/blob/master/Documentation/MANPAGE.md

ashjas

comment created time in 15 hours

pull request commentdokku/dokku

Do not remove unused image to hold tags

Yes.

tribela

comment created time in 18 hours

pull request commentdokku/dokku

Do not remove unused image to hold tags

So if I want to deploy new image, execute git:from-image command after pushing into docker registry?

tribela

comment created time in 18 hours

pull request commentdokku/dokku

Do not remove unused image to hold tags

Docs here: https://dokku.com/docs/deployment/methods/git/#initializing-an-app-repository-from-a-docker-image

You will need to push the image to a registry and login as the dokku user.

tribela

comment created time in 18 hours

pull request commentdokku/dokku

Do not remove unused image to hold tags

Oh I didn't know that git:tags was deprecated and git:from-image command. I want to move to that from-image deploy Cause I build the docker image separately with CI. Can you tell me how the git:from-image triggers to update(pull) to new image?

tribela

comment created time in 18 hours

pull request commentdokku/dokku

Do not remove unused image to hold tags

I don't think we should do this, as it will lead to folks having a ton of used up space and complaints that Dokku is leaving unused images around. Since the image is tagged with dokku's internal tag, I think we should assume Dokku is handling it's lifecycle.

Instead, it might be worth moving your workflow to the new git:from-image command?

tribela

comment created time in 18 hours

pull request commentdokku/dokku

Do not remove unused image to hold tags

That "unused" means "currently not running images". tags should not be removed even they are not running right now

tribela

comment created time in 19 hours

issue commentdocker/compose

Hooks to run scripts on host before starting any containers

Maybe this is useful to some folks: https://github.com/jvasile/docker-wrap

Jamie-

comment created time in a day

pull request commentdjango-cms/django-cms

Add support for Django 3.2

@FinalAngel @macolo can you have a look?

vinitkumar

comment created time in a day

issue commentdocker/compose

docker compose does not honor build arg while docker-compose does

Building with explicit --build-arg works as expected.

princemaple

comment created time in a day

issue commentdocker/compose

Proposal: make project-name persistent.

Hi! I would like to know, is this a beginner friendly issue? If yes , I would be really happy to wo rk😄

thaJeztah

comment created time in a day

issue commentdocker/compose

Hooks to run scripts on host before starting any containers

Would also be great if it could set environment variables in the up script. And then later on use these to further configure the services.

Jamie-

comment created time in a day

created repositoryroyaloperahouse/royaloperahouse.github.io

royaloperahouse.github.io

created time in a day

MemberEvent

issue commentdocker/compose

Docker-compose: Large port definitions exceed request timeout

I see the same with Ubuntu 20.04.2 running Docker version 20.10.6, build 370c289. Service startup times with docker-compose up are proportional to the number of port bindings defined in docker-compose.yaml. In other words there's a linear relationship between the number of port bindings and service start times. The same is true for docker-compose down.

CafeLungo

comment created time in a day

issue commentdocker/compose

Docker-compose: Large port definitions exceed request timeout

I see similar behavior starting with Docker Desktop (Mac) 3.3.0; I have downgraded to 3.2.2 and do not have the issue. Delay works out to approx. 1 sec/port defined. My normal port ranges include 40 ports per container, for 5 containers. The behavior I observe is thus a delay of about 2.5 minutes total, before any of these containers start up; then they start up in rapid order after that delay. When I reduced to ~6 ports per container, the delay was reduced to about 30 sec total.

Other devs on my team have reported similar behavior on linux environment, albeit not quite the same delay time.

OS: macOS 10.15.7 Docker via Docker Desktop, 3.3.0 and 3.3.3 confirmed 2018 MBPro, 6-core Intel i7, 15GB RAM

CafeLungo

comment created time in a day

issue commentdocker/compose

docker compose does not honor build arg while docker-compose does

I think this might be related to this problem (specifically for IPv4 addresses): https://stackoverflow.com/questions/67318361/docker-compose-ignoring-ipv4-address-in-container, that I just bumped into myself as well (on macOS Catalina):

docker-compose version:

docker-compose version 1.29.1, build c34c88b2
docker-py version: 5.0.0
CPython version: 3.9.0
OpenSSL version: OpenSSL 1.1.1h  22 Sep 2020

docker version:

Client:
 Cloud integration: 1.0.14
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.16.3
 Git commit:        370c289
 Built:             Fri Apr  9 22:46:57 2021
 OS/Arch:           darwin/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8728dd2
  Built:            Fri Apr  9 22:44:56 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
princemaple

comment created time in a day

issue commentdokku/dokku

After cleanup step the application restarts building wrong buildpack and fails

Hi @josegonzalez, Thanks a lot of your reply. Apologize for my delayed response.

git push -vvv deploy-axapp-v2 feature/bs5-framework:master

I ran the command you gave. Its the same response. Here the output from the exact command you asked me to run. https://gist.github.com/amitjindal/246af4390b1eb9f49ab4c07b3a12d7ea

Please note that in my repo I do not have the pre-docker or ver-2.9 branches. They are tags. For some reason this works fine on an older instance of the same application on the same dokku server.

In fact the application even starts and runs. However the repo shows no log on dokku server.

What should I try next? Should I delete the application and try to create again? Or should I check something else?

Thanks & Regards Amit

amitjindal

comment created time in a day

Pull request review commentdivio/divio-cloud-docs

Updated celery environment variable with rmq configuration

 If you make any local changes to a application's configuration that need to be a Environment variables --------------------- -When Celery is enabled for your application, two new environment variables will be configured:--* ``BROKER_URL``-* ``RABBITMQ_ERLANG_COOKIE``+When Celery is enabled for your application, a new environment variable ``DEFAULT_AMQP_BROKER_URL`` will be configured.+(In Aldryn Celery it is called ``BROKER_URL``).

"(It's also provided as BROKER_URL for legacy Aldryn Celery applications.)

mebdivio

comment created time in a day

Pull request review commentdivio/divio-cloud-docs

Updated celery environment variable with rmq configuration

 Set up local environment variables  In ``.env-local`` add:: -    RABBITMQ_ERLANG_COOKIE=secret_cookie_value-    BROKER_URL="amqp://guest:guest@rabbitmq:5672/"+    DEFAULT_AMQP_BROKER_URL="amqp://guest:guest@rabbitmq:5672/" -(Don't confuse the port ``5672`` of the RabbitMQ server with the port ``15672`` of its management interface.)+..  note::++    Applications using Aldryn Celery will require the environment variable ``DEFAULT_AMQP_BROKER_URL`` to be called+    ``BROKER_URL``.

"For legacy Aldryn Celery applications, name the environment variable BROKER_URL instead of DEFAULT_AMQP_BROKER_URL."

mebdivio

comment created time in a day

Pull request review commentdivio/divio-cloud-docs

Updated celery environment variable with rmq configuration

 the provision made on our cloud. A complete set-up would include: Locally, the four new containers will be set up as new services using the :ref:`docker-compose.yml <docker-compose-yml-reference>` file. -Note that in the cloud environment, the Celery-related containers are launched automatically. They, and the AMPQ message queue, are-not directly accessible. All monitoring and interaction must be handled via the main application running in the ``web``-container(s). The :ref:`docker-compose file is not used on the cloud <docker-compose-local>`.+Note that in the cloud environment, the Celery-related containers are launched automatically. They, and the AMPQ message+queue, are not directly accessible. All monitoring and interaction must be handled via the main application running in+the ``web`` container(s). The :ref:`docker-compose file is not used on the cloud <docker-compose-local>`. -Your application will already have other services listed in its ``docker-compose.yml``. Each of the new services will be need to be-added in a similar way.+Your application will already have other services listed in its ``docker-compose.yml``. Each of the new services will be+need to be added in a similar way.

Wording needs to be corrected.

mebdivio

comment created time in a day

Pull request review commentdivio/divio-cloud-docs

Updated celery environment variable with rmq configuration

 For the worker and scheduling containers, your application needs an executable a     [ $1 = "beat" ] ; then         celery -A path.to.celery.app beat --loglevel=INFO     else-        celery -A path.to.celery.app worker --concurrency=4 --loglevel=INFO --without-gossip --without-mingle --without-heartbeat -Ofair+        celery -A path.to.celery.app worker --concurrency=4 --loglevel=INFO --without-gossip --without-mingle+        --without-heartbeat -Ofair     fi  Note the paths that you will need to specify yourself. -Similarly, on deployment the infrastructure invokes (by default) a Django management command ``python manage.py celerycam`` to-start up the monitoring container.+Similarly, on deployment the infrastructure invokes (by default) a Django management command ``python manage.py+celerycam`` to start up the monitoring container. -* If you don’t want to use a monitoring container, please inform us, so that we can configure your application to start up without-  issuing the command (deployments will fail if the command fails)-* If you do want to use a monitoring container, you will need to add a ``celerycam`` management command to your application. The-  command needs to respond to the invocation: ``python manage.py celerycam --frequency=10 --pidfile=``.+* If you don’t want to use a monitoring container, please inform us, so that we can configure your application to start+up without issuing the command (deployments will fail if the command fails)

Line is missing a .

mebdivio

comment created time in a day

Pull request review commentdivio/divio-cloud-docs

Updated celery environment variable with rmq configuration

 For the worker and scheduling containers, your application needs an executable a     [ $1 = "beat" ] ; then         celery -A path.to.celery.app beat --loglevel=INFO     else-        celery -A path.to.celery.app worker --concurrency=4 --loglevel=INFO --without-gossip --without-mingle --without-heartbeat -Ofair+        celery -A path.to.celery.app worker --concurrency=4 --loglevel=INFO --without-gossip --without-mingle+        --without-heartbeat -Ofair

Don't reformat code; this will break.

mebdivio

comment created time in a day

Pull request review commentdivio/divio-cloud-docs

Updated celery environment variable with rmq configuration

 These tasks are covered in order below. Using the broker environment variable ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -For Celery, we provide a ``DEFAULT_AMQP_BROKER_URL`` (in some older applications, simply ``BROKER_URL``). This provides+For Celery, we provide a ``DEFAULT_AMQP_BROKER_URL`` (in Aldryn celery, simply ``BROKER_URL``). This provides

It's not that we provide a different env var, it's just that Aldryn Celery uses a different one. So you can say

... (the same value is also available as `BROKER_URL`, provided for legacy Aldryn Celery applications).
mebdivio

comment created time in a day

Pull request review commentdivio/divio-cloud-docs

Updated celery environment variable with rmq configuration

 These tasks are covered in order below. Using the broker environment variable ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -For Celery, we provide a ``DEFAULT_AMQP_BROKER_URL`` (in some older applications, simply ``BROKER_URL``). This provides+For Celery, we provide a ``DEFAULT_AMQP_BROKER_URL`` (in Aldryn celery, simply ``BROKER_URL``). This provides

Celery with capital C.

mebdivio

comment created time in a day

Pull request review commentdivio/divio-cloud-docs

Updated celery environment variable with rmq configuration

 How to configure Celery =======================  -This article assumes that you are already familiar with the basics of using Celery with Django and that you have Celery installed-in your application.+This article assumes that you are already familiar with the basics of using Celery with Django and that you have Celery+installed in your application.

If you can avoid introducing formatting changes, it's better. Otherwise the reviewer has to read through irrelevant changes.

mebdivio

comment created time in a day