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

Back to single volume #39

Closed
felixklauke opened this issue Aug 3, 2019 · 3 comments
Closed

Back to single volume #39

felixklauke opened this issue Aug 3, 2019 · 3 comments
Assignees

Comments

@felixklauke
Copy link
Owner

At the moment there are 5 volumes. I would like to merge them back to one to reduce complexity.

@felixklauke felixklauke self-assigned this Aug 3, 2019
@juresyahya
Copy link

any specific reason why you split it into 5 different volumes in the first place?

@felixklauke
Copy link
Owner Author

felixklauke commented Aug 4, 2019

TL;DR: Distributed Storage

@juresyahya Yeah that was a specific request of a user. Usually most users will use Volumes as "FIre & Forget". They will be created once and only be used at an active container. This user wanted to edit plugins & configs without mounting a volume in a container. But he still didn't want to deal with worlds. When you have more volumes you can distribute the content.
You can, for example, use NAS storage for the world but keep the configs in a mounted host folder, so you can edit them locally more easily. More volumes are more flexible when you want to have control over a specific type of data.

But I'm not sure anymore, that this make it easier.

@felixklauke
Copy link
Owner Author

After further considerations this will be delayed or not even done at all.

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