Hi. There are database changes between our release and version 2.7.3 of Mayan upstream. The database changes in our release correspond to unpublished changes already in Mayan upstream. But, if you migrate your database and Mayan EDMS version 2.8 doesn't pull all of our changes you could end up with an incompatible database. If you have a large number of critical documents I suggest you wait until Mayan upstream revise and merge our changes.
1. The data migration will happen automatically. It is performed by the Docker image itself when it encounters and existing database. 2. Both Docker images (the official one and ours) support S3 object storage out of the box. 3. It is not our intention to take over the project. That said, if Roberto asks us to, I think we would. I already manage several department installations of Mayan in our company as part of my day job. Maintaining the Mayan project would not be outside of what I and Michael already do daily. We try not to bother Roberto much, things in Puerto Rico are very bad. I will not go into details, it is not my place. Some of what they are dealing with => http://www.foxnews.com/politics/2018/03/09/storm-dealt-puerto-rico-knockout-blow-after-decades-fiscal-failure-corruption.html On Thursday, March 8, 2018 at 8:53:12 PM UTC-4, David Kornahrens wrote: > > Hey Eric, > Nice work. I just finished looking over some of your commits in the > gitlab. We currently are running the latest MayanEDMS and have a rather > large inventory loaded in. Couple of questions. > > 1. Are we able to upgrade to NG without losing the data? Anyway to > migrate the data? > 2. We have offloading media to S3 using the Django offload method from > Mayan. > 3. We haven't heard from Roberto in awhile, are you going to be taking > over the development of Mayan? > > Thanks, > David > > On Thursday, March 8, 2018 at 7:20:32 PM UTC-5, ericr...@gmail.com wrote: >> >> Awesome! Make sure you use Docker named volumes for the data. It is a >> current limitation that I hope to correct soon. >> >> On Thursday, March 8, 2018 at 2:45:59 PM UTC-4, Raul wrote: >>> >>> I was able to get it working by building it by myself with >>> docker-compose. >>> Nice jobs guys :) >>> >>> >>> Am Donnerstag, 8. März 2018 19:09:57 UTC+1 schrieb Raul: >>>> >>>> I just tried to start run that image. However, it stucks in a rebooting >>>> loop. >>>> Do you know what I can do? >>>> Is the image working? >>>> >>>> Thanks >>>> >>>> Am Donnerstag, 1. März 2018 09:45:37 UTC+1 schrieb ericr...@gmail.com: >>>>> >>>>> The Docker image is available from the Docker Hub at: >>>>> https://hub.docker.com/r/mayanedmsng/mayanedmsng/ >>>>> >>>>> Every procedure is the same as with the upstream version with the only >>>>> change that the repository reference must be mayanedmsng/mayanedmsng >>>>> instead of mayanedms/mayanedms. >>>>> >>>>> Once change this image has is that is includes a fourth worker to >>>>> handle the OCR and parsing queues. This worker is run with the lowest >>>>> possible process priority (19). Therefore OCR results might take longer >>>>> than with the upstream image. The advantage is that the OCR will not >>>>> slowdown the execution of the rest of the program. The total image layers >>>>> were reduced from 54 to 44. Total image size remained the same 1.32GB and >>>>> 490.8MB compressed (the actual download). >>>>> >>>>> Other changes according to Docker's best practices were made (pinning >>>>> installs to a specific version, not running dist-upgrade, etc). >>>>> >>>>> The repository for this image is here: >>>>> https://gitlab.com/e.riggs/mayan-edms-docker/commits/master >>>>> >>>>> I will continue working on getting the size of the image down. I'll >>>>> also keep trying using other base images instead of Ubuntu and or update >>>>> to >>>>> a more recent version of Ubuntu, as time allows. >>>>> >>>>> >>>>> -- --- 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.
