Skip to content

Reconsidering Single Volumes #64

@Huskydog9988

Description

@Huskydog9988

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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions