Re: [Mayan EDMS: 1750] Re: Paid support

[Cédric MARCOUX]

Yup, true :)

Envoyé de mon iPhone

> Le 2 juin 2017 à 05:06, Roberto Rosario  
> a écrit :
> 
> Yes, it has. These recent code commits are a direct result of the discussions 
> with Cédric and other support subscribers.
> 
> https://gitlab.com/mayan-edms/mayan-edms/commit/ce563bfb6a2b66257610d12f39b7ebca7e08f5e5
> https://gitlab.com/mayan-edms/mayan-edms/commit/61fd28319a9adf03ec6de65e82c743667ba921e2
> https://gitlab.com/mayan-edms/mayan-edms/commit/26b6fcae155d399b65186590f5d55cbd6248ec8e
> And the interim version 2.3 to be released to include these changes.
> 
> Support subscriber's feature requests get top priority but the discussions 
> are not public.
> 
>> On Thursday, June 1, 2017 at 10:12:30 PM UTC-4, David Kornahrens wrote:
>> Was this ever resolved?  I'm thinking about getting a support account, but 
>> want to make sure it's actually being utilized and available.
>> 
>>> On Wednesday, May 10, 2017 at 3:57:14 PM UTC-4, Cédric MARCOUX wrote:
>>> Hello,
>>> 
>>> i have paid the support with paypal but not receive any further instruction.
>>> I have sent a mail to i...@mayan-edms.com but not receive any answer.
>>> 
>>> How can I join the paid support? Thanks for your help
> 
> -- 
> 
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Mayan EDMS" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/mayan-edms/0cE2jeOVP-U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> mayan-edms+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1750] Re: Mayan EDMS Docker image updates

[Roberto Rosario]

Hi David,

When using Docker the database, documents and settings are kept in separate 
volumes. The volumes are persistent and remain after version upgrades.
The current image is being used in production without issues, in fact users 
report more success with the Docker image than trying the advanced 
deployment themselves and the OS, Django and Python experience it requires.

As mentioned in the original post, new improvements are being made to the 
image including being able to use a Postgresql database or container 
instead of the default SQLite to improve performance and data protection.

On Thursday, June 1, 2017 at 9:24:29 PM UTC-4, David Kornahrens wrote:
>
> 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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1747] Re: Paid support

[David Kornahrens]

Was this ever resolved?  I'm thinking about getting a support account, but 
want to make sure it's actually being utilized and available.

On Wednesday, May 10, 2017 at 3:57:14 PM UTC-4, Cédric MARCOUX wrote:
>
> Hello,
>
> i have paid the support with paypal but not receive any further 
> instruction.
> I have sent a mail to i...@mayan-edms.com but not receive any answer.
>
> How can I join the paid support? Thanks for your help
>

-- 

--- 
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mayan EDMS: 1747] Re: Mayan EDMS Docker image updates

[David Kornahrens]

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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.