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
Using the regular three container setup, everything is working the way I want it. However, we are looking at adding a new container which requires special nginx configuration settings (satisfy and auth_*, to be exact). The setup creates automatic configs, and we don't want to modify the template, since that would also mess with our other containers which don't need it, but is there a workflow where I can have this setup work as intended for all other containers but still specify my own specific nginx config file for one specific host ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Using the regular three container setup, everything is working the way I want it. However, we are looking at adding a new container which requires special nginx configuration settings (
satisfy
andauth_*
, to be exact). The setup creates automatic configs, and we don't want to modify the template, since that would also mess with our other containers which don't need it, but is there a workflow where I can have this setup work as intended for all other containers but still specify my own specific nginx config file for one specific host ?Beta Was this translation helpful? Give feedback.
All reactions