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
Not sure if this is possible or I misunderstood the concept of the nexGen Modules, but I'm trying to pass some options usign nginx:vhosts { … } to use in my custom template but this is not possible. I get Invalid parameter options at …
It's not the concept of these modules to be customizable ? How this can be achieved ?
I've seen that I can set some options in the nginx main class but obviously the important thing is to set them in the vhost file. I can do it setting the vars outside but the problem comes when you want to set multiples vhosts.
Sorry if this is possible but I couldn't find it in your web and manuals.
Thanks for sharing ;) these are great.
The text was updated successfully, but these errors were encountered:
Actually the option_lookup function currently works only for the main class of module and not, as in this case, for a subclass or a define.
I do agree, anyway, that it would be interesting to have it also for defines like nginx::vhost (given that is added the 'options' parameter), so I would consider this an open feature request.
Not sure if this is possible or I misunderstood the concept of the nexGen Modules, but I'm trying to pass some options usign nginx:vhosts { … } to use in my custom template but this is not possible. I get
Invalid parameter options at …
It's not the concept of these modules to be customizable ? How this can be achieved ?
I've seen that I can set some options in the nginx main class but obviously the important thing is to set them in the vhost file. I can do it setting the vars outside but the problem comes when you want to set multiples vhosts.
Sorry if this is possible but I couldn't find it in your web and manuals.
Thanks for sharing ;) these are great.
The text was updated successfully, but these errors were encountered: