You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most people using this container are wanting to use it to share something that has been made available to the container using a mapped volume. Accessing and editing the config.yml from inside the container can be difficult, depending on your linux knowledge.
My suggestion is that by default, on first build, if it doesn't already exist, a /data/config.yml is created that is configured to share the /data folder in a public share. It could also contain a commented section with a full config example for reference.
This would enable users to immediately remotely access and edit the config.yml to suit their needs, just restarting the container for the new config to take effect.
The text was updated successfully, but these errors were encountered:
Not a bug, just an idea.
Most people using this container are wanting to use it to share something that has been made available to the container using a mapped volume. Accessing and editing the
config.yml
from inside the container can be difficult, depending on your linux knowledge.My suggestion is that by default, on first build, if it doesn't already exist, a
/data/config.yml
is created that is configured to share the/data
folder in a public share. It could also contain a commented section with a full config example for reference.This would enable users to immediately remotely access and edit the
config.yml
to suit their needs, just restarting the container for the new config to take effect.The text was updated successfully, but these errors were encountered: