-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Simplify volume mounts #260
Comments
I've deployed the application using a single volume mounted to the |
@MeurillonGuillaume the only thing stopping the app from being able to be fully deployed in a single volume is the data protection keys which has to live in As for the docker compose...yeah, it's pretty outdated and I ought to update it someday, it was created a long time ago, but there are concerns about existing users missing their data if they are updating from multi volume to single volume since their data won't be in there. I'm still going to leave this ticket open because it's not fully capable of running on a single volume due to the data protection keys volume. |
Care to share? |
@Judman this should work.
@iloveicedgreentea I'm not sure if it's possible to simplify it even further, so I'll be closing this issue since this is about the closest we can get to a single volume. |
@hargata Have you tried to store /DataProtection-Keys in the lubelog volume and create a link to this directory.
(with proper creation and initialization of the DataProtection-Keys directory) Then it would be a true single volume |
As pointed in the #407 issue, this a pretty bad idea to make /app de volume. |
@redge76 that makes sense, I'll re-open this ticket, but making this a single volume app is not going to be prioritized anytime soon. |
To reduce operational burden and make it simpler to deploy, there should only be one volume needed like /app or something, and the application should then deal with having the right folders in place.
Love the tool thanks for making it
The text was updated successfully, but these errors were encountered: