[Mayan EDMS: 2452] Version 3.0 beta 2 out

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2452] Version 3.0 beta 2 out

rosarior
Administrator
New beta version out. With this beta the hope is to get feedback about the new way Mayan EDMS installs and the new way the Docker image is produce and hosted.

Previously, a blank "media" folder was committed to the repository. This folder is used to store document files, image caches and document signatures. User settings were managed using a local.py module in the "settings" folder.
This created a difficult situation where there had to be a writable directory committed to the repository. This also meant having to do use some tricks to allow the initial setup to complete even thought there was no user setting file and no secret key available, something Django doesn't allow. The way Mayan solved this was by reverting to a default setting file when there was no user settings file. With this new beta, now even the user setting will be stored in the "media" folder inside an additional "settings" folder. This way all installation artifacts are now contained in a separate directory that is not part of the code repository. This also allows recreating this entire media folder at runtime, thus removing the requirement of the Docker image to only used named volumes. 

Another change for this beta is that the Docker repository is now merged back into the main repository. Until now only stable release were available as Docker images. This is because these releases were done manually. After a stable Mayan Python package was released, the Docker repository was updated and pushed to BitBucket which in turn triggered the automated creation of a new image in the Docker registry. This meant that when errors with the Docker image were found we sometimes had to go back to the Mayan Python code repository, make changes, make another release, and return to the continue work on the Docker repository. Now that the Docker image creation is part of the main repository this happens in the same debugging process. 

Another change is that we are now using GitLab's Docker registry to generate the Docker images. The images are also automatically generated when the test suit completes without error. This means that for each successful commit of new code a new daily docker images will be available. This allows for continuous deliver of Docker images. The images are tagged with the branch that was used to generate them and can be found here: https://gitlab.com/mayan-edms/mayan-edms/container_registry When you checkout image "registry.gitlab.com/mayan-edms/mayan-edms:feature-docker" you will be pulling the latest image built from code from the "feature/docker" branch. The image "registry.gitlab.com/mayan-edms/mayan-edms:versions-next" will be from code from the "versions/next" branch, the branch with the latest development code that will become the next stable release. When a stable release happens the images will be tagged with the version number and a special tagged named "latest" will point to the latest release. This setup allows the production of nightly as well as stable images using the same setup. To try out the latest development image use:

docker pull registry.gitlab.com/mayan-edms/mayan-edms:versions-next

docker run -d --name mayan-edms-nightly --restart=always -p 8000:8000 -v /docker-volumes/mayan-nightly:/var/lib/mayan registry.gitlab.com/mayan-edms/mayan-edms:versions-next 

Since the gunicorn app server is now used instead of NGINX the default port has changed to 8000. This change is internal to the Docker container. Docker port mapping can still be used to present port 8000 of the container as port 80 of the machine by using -p 80:8000.  

The documentation for the Docker image will be merged as a chapter of the main documentation. 



--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2455] Re: Version 3.0 beta 2 out

Olimpiu Rob
I'm missing the static resources when running the latest docker image.

On Friday, 11 May 2018 06:54:35 UTC+3, Roberto Rosario wrote:
New beta version out. With this beta the hope is to get feedback about the new way Mayan EDMS installs and the new way the Docker image is produce and hosted.

Previously, a blank "media" folder was committed to the repository. This folder is used to store document files, image caches and document signatures. User settings were managed using a local.py module in the "settings" folder.
This created a difficult situation where there had to be a writable directory committed to the repository. This also meant having to do use some tricks to allow the initial setup to complete even thought there was no user setting file and no secret key available, something Django doesn't allow. The way Mayan solved this was by reverting to a default setting file when there was no user settings file. With this new beta, now even the user setting will be stored in the "media" folder inside an additional "settings" folder. This way all installation artifacts are now contained in a separate directory that is not part of the code repository. This also allows recreating this entire media folder at runtime, thus removing the requirement of the Docker image to only used named volumes. 

Another change for this beta is that the Docker repository is now merged back into the main repository. Until now only stable release were available as Docker images. This is because these releases were done manually. After a stable Mayan Python package was released, the Docker repository was updated and pushed to BitBucket which in turn triggered the automated creation of a new image in the Docker registry. This meant that when errors with the Docker image were found we sometimes had to go back to the Mayan Python code repository, make changes, make another release, and return to the continue work on the Docker repository. Now that the Docker image creation is part of the main repository this happens in the same debugging process. 

Another change is that we are now using GitLab's Docker registry to generate the Docker images. The images are also automatically generated when the test suit completes without error. This means that for each successful commit of new code a new daily docker images will be available. This allows for continuous deliver of Docker images. The images are tagged with the branch that was used to generate them and can be found here: <a href="https://gitlab.com/mayan-edms/mayan-edms/container_registry" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcontainer_registry\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH_XrCVBA-ao53xpO3tPfafdlgsnA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcontainer_registry\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH_XrCVBA-ao53xpO3tPfafdlgsnA&#39;;return true;">https://gitlab.com/mayan-edms/mayan-edms/container_registry When you checkout image "<a href="http://registry.gitlab.com/mayan-edms/mayan-edms:feature-docker" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Afeature-docker\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNErTT65yIN_jCrfD6oSgDZDMSJuPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Afeature-docker\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNErTT65yIN_jCrfD6oSgDZDMSJuPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:feature-docker" you will be pulling the latest image built from code from the "feature/docker" branch. The image "<a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next" will be from code from the "versions/next" branch, the branch with the latest development code that will become the next stable release. When a stable release happens the images will be tagged with the version number and a special tagged named "latest" will point to the latest release. This setup allows the production of nightly as well as stable images using the same setup. To try out the latest development image use:

docker pull <a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next

docker run -d --name mayan-edms-nightly --restart=always -p 8000:8000 -v /docker-volumes/mayan-nightly:/var/lib/mayan <a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next 

Since the gunicorn app server is now used instead of NGINX the default port has changed to 8000. This change is internal to the Docker container. Docker port mapping can still be used to present port 8000 of the container as port 80 of the machine by using -p 80:8000.  

The documentation for the Docker image will be merged as a chapter of the main documentation. 



--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2456] Re: Version 3.0 beta 2 out

Olimpiu Rob
The /static/appearance/node_modules/ is missing, the rest seem to be loading

On Friday, 11 May 2018 11:21:47 UTC+3, Olimpiu Rob wrote:
I'm missing the static resources when running the latest docker image.

On Friday, 11 May 2018 06:54:35 UTC+3, Roberto Rosario wrote:
New beta version out. With this beta the hope is to get feedback about the new way Mayan EDMS installs and the new way the Docker image is produce and hosted.

Previously, a blank "media" folder was committed to the repository. This folder is used to store document files, image caches and document signatures. User settings were managed using a local.py module in the "settings" folder.
This created a difficult situation where there had to be a writable directory committed to the repository. This also meant having to do use some tricks to allow the initial setup to complete even thought there was no user setting file and no secret key available, something Django doesn't allow. The way Mayan solved this was by reverting to a default setting file when there was no user settings file. With this new beta, now even the user setting will be stored in the "media" folder inside an additional "settings" folder. This way all installation artifacts are now contained in a separate directory that is not part of the code repository. This also allows recreating this entire media folder at runtime, thus removing the requirement of the Docker image to only used named volumes. 

Another change for this beta is that the Docker repository is now merged back into the main repository. Until now only stable release were available as Docker images. This is because these releases were done manually. After a stable Mayan Python package was released, the Docker repository was updated and pushed to BitBucket which in turn triggered the automated creation of a new image in the Docker registry. This meant that when errors with the Docker image were found we sometimes had to go back to the Mayan Python code repository, make changes, make another release, and return to the continue work on the Docker repository. Now that the Docker image creation is part of the main repository this happens in the same debugging process. 

Another change is that we are now using GitLab's Docker registry to generate the Docker images. The images are also automatically generated when the test suit completes without error. This means that for each successful commit of new code a new daily docker images will be available. This allows for continuous deliver of Docker images. The images are tagged with the branch that was used to generate them and can be found here: <a href="https://gitlab.com/mayan-edms/mayan-edms/container_registry" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcontainer_registry\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH_XrCVBA-ao53xpO3tPfafdlgsnA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcontainer_registry\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH_XrCVBA-ao53xpO3tPfafdlgsnA&#39;;return true;">https://gitlab.com/mayan-edms/mayan-edms/container_registry When you checkout image "<a href="http://registry.gitlab.com/mayan-edms/mayan-edms:feature-docker" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Afeature-docker\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNErTT65yIN_jCrfD6oSgDZDMSJuPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Afeature-docker\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNErTT65yIN_jCrfD6oSgDZDMSJuPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:feature-docker" you will be pulling the latest image built from code from the "feature/docker" branch. The image "<a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next" will be from code from the "versions/next" branch, the branch with the latest development code that will become the next stable release. When a stable release happens the images will be tagged with the version number and a special tagged named "latest" will point to the latest release. This setup allows the production of nightly as well as stable images using the same setup. To try out the latest development image use:

docker pull <a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next

docker run -d --name mayan-edms-nightly --restart=always -p 8000:8000 -v /docker-volumes/mayan-nightly:/var/lib/mayan <a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next 

Since the gunicorn app server is now used instead of NGINX the default port has changed to 8000. This change is internal to the Docker container. Docker port mapping can still be used to present port 8000 of the container as port 80 of the machine by using -p 80:8000.  

The documentation for the Docker image will be merged as a chapter of the main documentation. 



--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2458] Re: Version 3.0 beta 2 out

Victor Zele
Will there still be a standard PIP install method for these packages or should I figure out how to change my installation from PIP to docker?

thanks for the hard work!

CONFIDENTIALITY NOTICE: 

This transmission may contain information which is Vimo, Inc. (DBA Getinsured) confidential and/or legally privileged. The information is intended only for the use of the individual or entity named on this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of the contents of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify me by return e-mail and destroy all copies of the original message.

--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2461] Re: Version 3.0 beta 2 out

rosarior
Administrator
In reply to this post by Olimpiu Rob
It seems the javascript download step is not executing. Will get on it. Thanks for testing!

On Friday, May 11, 2018 at 4:36:06 AM UTC-4, Olimpiu Rob wrote:
The /static/appearance/node_modules/ is missing, the rest seem to be loading

On Friday, 11 May 2018 11:21:47 UTC+3, Olimpiu Rob wrote:
I'm missing the static resources when running the latest docker image.

On Friday, 11 May 2018 06:54:35 UTC+3, Roberto Rosario wrote:
New beta version out. With this beta the hope is to get feedback about the new way Mayan EDMS installs and the new way the Docker image is produce and hosted.

Previously, a blank "media" folder was committed to the repository. This folder is used to store document files, image caches and document signatures. User settings were managed using a local.py module in the "settings" folder.
This created a difficult situation where there had to be a writable directory committed to the repository. This also meant having to do use some tricks to allow the initial setup to complete even thought there was no user setting file and no secret key available, something Django doesn't allow. The way Mayan solved this was by reverting to a default setting file when there was no user settings file. With this new beta, now even the user setting will be stored in the "media" folder inside an additional "settings" folder. This way all installation artifacts are now contained in a separate directory that is not part of the code repository. This also allows recreating this entire media folder at runtime, thus removing the requirement of the Docker image to only used named volumes. 

Another change for this beta is that the Docker repository is now merged back into the main repository. Until now only stable release were available as Docker images. This is because these releases were done manually. After a stable Mayan Python package was released, the Docker repository was updated and pushed to BitBucket which in turn triggered the automated creation of a new image in the Docker registry. This meant that when errors with the Docker image were found we sometimes had to go back to the Mayan Python code repository, make changes, make another release, and return to the continue work on the Docker repository. Now that the Docker image creation is part of the main repository this happens in the same debugging process. 

Another change is that we are now using GitLab's Docker registry to generate the Docker images. The images are also automatically generated when the test suit completes without error. This means that for each successful commit of new code a new daily docker images will be available. This allows for continuous deliver of Docker images. The images are tagged with the branch that was used to generate them and can be found here: <a href="https://gitlab.com/mayan-edms/mayan-edms/container_registry" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcontainer_registry\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH_XrCVBA-ao53xpO3tPfafdlgsnA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcontainer_registry\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH_XrCVBA-ao53xpO3tPfafdlgsnA&#39;;return true;">https://gitlab.com/mayan-edms/mayan-edms/container_registry When you checkout image "<a href="http://registry.gitlab.com/mayan-edms/mayan-edms:feature-docker" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Afeature-docker\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNErTT65yIN_jCrfD6oSgDZDMSJuPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Afeature-docker\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNErTT65yIN_jCrfD6oSgDZDMSJuPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:feature-docker" you will be pulling the latest image built from code from the "feature/docker" branch. The image "<a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next" will be from code from the "versions/next" branch, the branch with the latest development code that will become the next stable release. When a stable release happens the images will be tagged with the version number and a special tagged named "latest" will point to the latest release. This setup allows the production of nightly as well as stable images using the same setup. To try out the latest development image use:

docker pull <a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next

docker run -d --name mayan-edms-nightly --restart=always -p 8000:8000 -v /docker-volumes/mayan-nightly:/var/lib/mayan <a href="http://registry.gitlab.com/mayan-edms/mayan-edms:versions-next" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fregistry.gitlab.com%2Fmayan-edms%2Fmayan-edms%3Aversions-next\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFd0kTiPD4cJRuPF11B7xJbvV4MPg&#39;;return true;">registry.gitlab.com/mayan-edms/mayan-edms:versions-next 

Since the gunicorn app server is now used instead of NGINX the default port has changed to 8000. This change is internal to the Docker container. Docker port mapping can still be used to present port 8000 of the container as port 80 of the machine by using -p 80:8000.  

The documentation for the Docker image will be merged as a chapter of the main documentation. 



--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2462] Re: Version 3.0 beta 2 out

rosarior
Administrator
In reply to this post by Victor Zele
The Python package will also be released too. The update is to allow us to release Docker images faster too but those won't substitute the Python package. 

Thank you for the feedback and supporting the project.

On Friday, May 11, 2018 at 11:05:51 AM UTC-4, Victor Zele wrote:
Will there still be a standard PIP install method for these packages or should I figure out how to change my installation from PIP to docker?

thanks for the hard work!

--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2467] Re: Version 3.0 beta 2 out

David Kornahrens
Hey Roberto --
Was this error for new installs?  Will we be fine to upgrade from an existing installation?

Thanks,
David

On Friday, May 11, 2018 at 3:18:39 PM UTC-4, Roberto Rosario wrote:
The Python package will also be released too. The update is to allow us to release Docker images faster too but those won't substitute the Python package. 

Thank you for the feedback and supporting the project.

On Friday, May 11, 2018 at 11:05:51 AM UTC-4, Victor Zele wrote:
Will there still be a standard PIP install method for these packages or should I figure out how to change my installation from PIP to docker?

thanks for the hard work!

--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2469] Re: Version 3.0 beta 2 out

Victor Zele
Anyone else getting the below errors when trying to delete documents or empty the trash?
It was definitely working on 2.7.3 release.

Thanks

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.



CONFIDENTIALITY NOTICE: 

This transmission may contain information which is Vimo, Inc. (DBA Getinsured) confidential and/or legally privileged. The information is intended only for the use of the individual or entity named on this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of the contents of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify me by return e-mail and destroy all copies of the original message.

--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[Mayan EDMS: 2515] Re: Version 3.0 beta 2 out

Andy Salnikov
Victor, I opened new thread for this error that I also see in 3.0.2: https://groups.google.com/forum/#!topic/mayan-edms/ZeBGsvba51w

On Monday, May 21, 2018 at 3:00:07 PM UTC-7, Victor Zele wrote:
Anyone else getting the below errors when trying to delete documents or empty the trash?
It was definitely working on 2.7.3 release.

Thanks

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.


--

---
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 [hidden email].
For more options, visit https://groups.google.com/d/optout.