Hello Roberto. We are new to your project, but have spun up a Docker image of Myan. We are attempting to run this in a production environment.
Few questions here: -Even though we are on the latest right now (we believe), what is the command to update the docker image without losing our data? -Is this ready for primetime? Thanks, David On Thursday, May 18, 2017 at 2:02:21 AM UTC-4, Roberto Rosario wrote: > > As part of the round of improvements to the next version of the Docker > image, a production stack using Docker compose has been included. > This stack will launch 4 containers: > > - A database container using Postgres > - A Celery broker container using RabbitMQ > - A Celery results container using Redis > - A Mayan EDMS container that uses the above service containers > > If you have experience building Docker images and using Docker compose, > please help test this stack on your hardware. > > Other improvements added: > > Allowing changing the database backend using the environment variables: > > - MAYAN_DATABASE_DRIVER, default: None > - MAYAN_DATABASE_NAME, default : 'mayan' > - MAYAN_DATABASE_USER, default: 'mayan' > - MAYAN_DATABASE_PASSWORD, default: '' > - MAYAN_DATABASE_HOST, default: None > - MAYAN_DATABASE_PORT, default: None > > The Celery broker and Celery results backend can also be changed using the > environment variables: > > - MAYAN_BROKER_URL, default: 'redis://127.0.0.1:6379/0' > - MAYAN_CELERY_RESULT_BACKEND, default: 'redis://127.0.0.1:6379/0' > > If the MAYAN_BROKER_URL and MAYAN_CELERY_RESULT_BACKEND are specified, the > built in > REDIS server is disabled in favor of the external Celery result backend. > > A new dedicated image converter worker was added to supervisor. This > allows for previews to be generated > and displayed even during high loads (such as when doing OCR on large > documents). > > The installation process was simplified and reduced to a single step: > > docker run -d --name mayan-edms --restart=always -p 80:80 -v > mayan_data:/var/lib/mayan mayanedms/next > > Gone is the initialization step. The image now keeps track of the state of > the data in the volume to determine whether to initialize and run > or upgrade and run when launched. > > The volume setup was also simplified and reduced to a single volume. The > settings and document storage files now co-exists in a single tree > inside a sngle volume. > > The NGINX web server limits for uploading files were increased to a max > file size of 500 MB and the upload timeout was increased to > 600 seconds (10 minutes). These are web server settings and don't affect > the overall memory usage of the container. > > If an external database is used, database connection keepalive is > automatically enabled with a default of 60 seconds. > This Django settings allows reusing database connections instead of > closing and opening database connection for each > HTTP request/response cycle. > > Finally a health check was added to allow other Docker images like reverse > proxies or load balancers to know when the Mayan EDMS container > is ready for traffic. > > To follow and test these improvements follow the 'development' branch of > the Docker repository at: > https://gitlab.com/mayan-edms/mayan-edms-docker/tree/development > > Please help test these changes to move them to the stable master branch as > soon as possible. > -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
