Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep user data in /usr/share/mayan-edms #34

Closed
DocCyblade opened this issue Oct 28, 2016 · 4 comments
Closed

Keep user data in /usr/share/mayan-edms #34

DocCyblade opened this issue Oct 28, 2016 · 4 comments
Assignees
Milestone

Comments

@DocCyblade
Copy link
Owner

Since we are backing up all of the app I think it would be best to keep the default data document directory. Per the Mayan Docs regarding backup/restore we really just need the documents and database. Putting the data back instead of /srv/edms-data/

If I do this, where should the demo-data folder go, as it currently is at /srv/edms-data/demo-data

@DocCyblade DocCyblade added this to the Beta 5 milestone Oct 28, 2016
@DocCyblade DocCyblade self-assigned this Oct 28, 2016
@DocCyblade
Copy link
Owner Author

@JedMeister - Thoughts on this? This would make backup plan simple, add one directory and exclude cache/pyc files.

@DocCyblade
Copy link
Owner Author

Also it would be in line with the Mayan upstream documentation as well

@JedMeister
Copy link
Collaborator

JedMeister commented Oct 28, 2016

Sounds fine to me.

Perhaps put the demo data in a similar location to the "real" data? Something like mayan/media/demo-data/?

DocCyblade pushed a commit that referenced this issue Oct 29, 2016
   - Change document storage location back to default (Issue #34)
   - Update DEMO data (Issue #37)
   - Workaround for Issue #38
      - setuptools v28.7 issue (pypa/setuptools#833)
   - Use specific version of Mayan EDMS for build (v2.1.4)
@DocCyblade
Copy link
Owner Author

Complete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants