A single bad project can break the nginx configuration and thus resulting in either q locked vhost-proxy config (if a valid config is already running) or a broken config (if vhost-proxy is started fresh/reset).
We need to adjust the config template to prevent such issues.
Details
$ fin docker logs docksal-vhost-proxy
...
2020/02/05 18:58:52 Error running notify command: proxyctl notify, exit status 1
2020/02/05 18:58:52 [proxyctl notify]: 2020/02/05 18:58:52 [emerg] 1060#1060: no servers are inside upstream in /etc/nginx/conf.d/vhosts.conf:224
2020/02/05 18:58:52 [proxyctl notify]: nginx: [emerg] no servers are inside upstream in /etc/nginx/conf.d/vhosts.conf:224
2020/02/05 18:58:52 [proxyctl notify]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed
...
A single bad project can break the nginx configuration and thus resulting in either q locked vhost-proxy config (if a valid config is already running) or a broken config (if vhost-proxy is started fresh/reset).
We need to adjust the config template to prevent such issues.
Details