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

Reconsidering Single Volumes #64

Open
Huskydog9988 opened this issue Dec 6, 2020 · 1 comment
Open

Reconsidering Single Volumes #64

Huskydog9988 opened this issue Dec 6, 2020 · 1 comment
Assignees

Comments

@Huskydog9988
Copy link

Is your feature request related to a problem? Please describe.
The complexity of juggling multiple volumes at once is entirely redundant. For the end user they have multiple different folders to juggle, all of which add unneeded complexity to a solution designed to reduce it. On the development side of things, it adds more folders and files to juggle for no explicate benefit.

Describe the solution you'd like
I would like the 5 volumes to be consolidated down into 1 simpler to manager volume.

Describe alternatives you've considered
A system could be implemented that allows for the end user to choose between a single volume or multiple volumes. I serious doubt this is a viable option, considering how it would have to be implemented, but none the less it is an alternative.

Additional context
This issue was discussed in issue #39. The reason why it was closed was very unclear, only stating it wasn't going to happen. Not going back to a single volume is a little beyond me at this moment. I understand it would take some refactoring of the Dockerfile, but in the end I feel this change would be of the upmost benefit in the long run.

@Huskydog9988 Huskydog9988 changed the title Single Volumes Reconsidering Single Volumes Dec 6, 2020
@felixklauke
Copy link
Owner

Providing a choice between a single and multi volume option is more confusing and less intuitive, I wouldn't recommend this. But there will definitely be a step back to one volume for simplicity reasons.

@felixklauke felixklauke self-assigned this Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants