Just a note on this, to clarify: nginx::vhost is supposed to be used as an
alternative to the defines in nginx::resource::* (so
nginx::resource::upstream should be used with nginx::resource::vhost) is
So changes there don't need to fit into nginx/manifests/vhost.pp


On Mon, Sep 30, 2013 at 6:41 PM, Jacob Hollenbeck
<notifications@github.com>wrote:

> In manifests/resource/upstream.pp:
>
> > +  case $::operatingsystem {
> > +    ubuntu,debian,mint: {
> > +      concat::fragment { "${vhost}+30-upstream-${name}.tmp":
> > +        ensure  => $ensure_real,
> > +        order   => '30',
> > +        content => template($template_upstream),
> > +        target  => "${nginx::config_dir}/sites-available/${vhost}.conf",
> > +        notify  => $nginx::manage_service_autorestart,
> > +      }
> > +    }
> > +    default: {
> > +      file { "${nginx::config_dir}/conf.d/${vhost}-upstream.conf":
> > +        ensure   => $ensure_real,
> > +        content  => template($template_upstream),
> > +      }
> > +    }
> >    }
>
> I guess this is more of an architectural problem. When using upstream with
> the vhost + location resources this works fine - however if using the
> upstream resource with the regular vhost, it does not...
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/example42/puppet-nginx/pull/36/files#r6662981>
> .
>