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
I think that was just to make config easier if the default /etc/nginx path wasn't used, and was introduced by d8e6d60.
There's no reason why you couldn't use the defined type as you described. PR welcome to add a upstream_config parameter to nginx::resource::upstream which defaults to "${nginx::config::conf_dir}/conf.d/${name}-upstream.conf". Or a more clever solution if you have one!
3flex
changed the title
Upstream requires nginx since 0.10
Upstream requires nginx since 0.1.0
Oct 1, 2014
3flex
changed the title
Upstream requires nginx since 0.1.0
Upstream requires nginx since 0.0.10
Oct 1, 2014
It looks like this pr introduces a change in the way upstream can be used.
I used to let applications defined their
upstream
in their configuration process. Later on thenginx
module might or might not be used.It looks like if I define an upstream only (without
vhost
orinclude nginx
) this line will fail because${nginx::config::conf_dir}
is undefined.Is this intended ?
The text was updated successfully, but these errors were encountered: