[Mayan EDMS: 1758] Status of Issue 139
Roberto, I submitted issue #139 to you quite a while ago, and I see that one of the prerequisites has been closed (Issue #178). Does this mean that #139 can be implemented now? Or are there other issues standing in the way? I need #139 on a current project of mine, and would like to use Mayan for this project. Is there a work around for issue #139? Thanks! Mark -- --- 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: 1758] cabinets permissions
Hi, I would like to attribute one cabinet for each users that I create but I dont want the users to be able to see each cabinets for exemple, I have created the users "John Carpenter" and "Mickey Redfield", which is part of the group "Client" which is a member of the role "classic user" I have set the permissions of "classic user" in this way : on the chapter Cabinets, I prohibited to create, edit, view, and delete cabinets then I made 2 cabinets : John Carpenter and MickeyRedfield, for the one of Mickey Redfield I allow the "view of cabinets" and I did the same for John Carpenter. Then when John Carpenter log in, he is able to go in his cabinets but can't go in the others, and vice versa The thing which is quite annoying, is that Mike can see that John is my client and same in the other way. Is there a tip to mask the name of the cabinet as well ? I think it's not logic to be able to see the cabinet whereas it's prohibited in the role permission what do you think ? can I do some thing for this ? -- --- 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: 1757] Re: Mayan EDMS Docker image updates
One more question Roberto -- Because I used the Docker deploy method, do I still update the same way "pip search mayan-edms" ? THank you, David -- --- 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: 1755] Re: Mayan EDMS Docker image updates
Outstanding. If the commit hasn't been packaged yet, me running the command will not do anything correct? -- --- 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: 1754] Multifunctional Printer Config (Xerox)
I have seen in the support documents that Multi-functional printers are accepted as a source for gathering documents. We have EDMS deployed in the cloud, how would we go about setting up a MF printer to serve our needs? Thx, David -- --- 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: 1753] Re: Mayan EDMS Docker image updates
Roberto - Is there a method in your program to verify we are on the latest product? And how do we check this via command line or some other interface? Thx, David -- --- 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: 1751] Re: Mayan EDMS Docker image updates
Thank you Roberto. We have spun up a Docker image with your product and have been building out our instance to fit our needs. We are impressed with the product so far. I'm sure I'll have some other questions. Once we get everything up and running, we plan to purchase a support contract with you for business use as we will most likely need some assistance. 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.
