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
The only real way to do this is to create a custom, derivative image of your own which has the settings you want. There are two ways to do this:
Simply fork the repo and make changes to the template in etc/nginx.conf.tpl.
Modify build.sh to contain the name of your custom repo (instead of garywiz/docker-grav).
Then, you can use your new repo with any new settings you wish.
I agree it would be nice to have more customization ,but it's hard to anticipate what people may need since there are so many possible areas.
One possibility would be to recognize that nginx.conf had been set to read-only and not overwrite it. Then, you could manually change the permissions to preserve it. Thoughts on that?
AFAIK the read-only attribute will not be preserved in a git repository. I would like to be able to deploy my site from git to a host directly.
My suggestion is to have an optional nginx.conf.custom file. This file would be detected on container startup. If it exists, it is used instead of default nginx.conf. Its contents could be even copied into nginx.conf if that makes things easier.
Similar functionality is needed also for sites.d/grav.conf
I would like to make following changes to nginx configuration:
What is the recommended way to do this? Right now any changes to nginx configuration get overwritten on container restart.
The text was updated successfully, but these errors were encountered: