-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[BUG] Config should have it own folder #902
Comments
Im having an issue with this as well. I bind the local to the hosted path but it forces me to put config.yml in the actual path (which makes no sense). I would expect to see /app/config/ and that is where the yml file is read from that way I can attach it to a volume etc. When you do /app/public/config.yml it actually creates a folder called config.yml with no config file in it, and when I added one it still didn't read or recognize it. |
Have already implemented this as part of #799 - but am just waiting until the rest of the ticket is completed before it will be merged (for version 2.1.2) |
This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days. |
This issue was automatically closed because it has been stalled for over 6 weeks with no activity. |
Environment
Self-Hosted (Docker)
System
n/a
Version
master
Describe the problem
Currently the config is a
conf.yml
file in `/app/public/.That works fine for a single file config when using containers (docker, k8s, ..)
If however you have a config in multiple files, you will need to mount the entire
/app/public
folder for your container to see all config files and this will shadow the rest of the files under/app/public
.Ideally the config folder should be configurable or set to a subfolder somewhere. That could be
/app/config
by default for instance. This would allow mapping/app/config
while not affecting the content of/app/public
(also the config should probably not be public).Additional info
No response
Please tick the boxes
The text was updated successfully, but these errors were encountered: