Puppet users - Jun 2011 - NGINX Puppet Module: Looking for Feedback/Use Cases

Hello everyone,

I''m currently working on a module for NGINX that I''d love to
get some input on. Code can be found here:
http://github.com/puppetlabs/puppetlabs-nginx.

This module is currently in development - it supports a few use cases: 
   * Create a vhost
   * Create multiple location references for a vhost
   * Create Proxy Upstream references to be used by Nginx
   * Allow SSL configuration (auto-generation of the SSL Cert is not supported
right now - not sure how useful this would be to folks)

Things that would also be useful that I''m immediately aware of:
   * Adding of rewrite rules
   * Adding regex support of a location 

* Other OS Support: Only various Linux distros have been tested as of right now.

My ask is this: I''m really interested in the various use cases of nginx
that are used by the community today that we can roll into this module.

Thanks!

-jamison

-- 
Jamison Fryman
jamison@puppetlabs.com
ph +1.615.669.2048 | twitter jfryman | gtalk: jamison@puppetlabs.com 

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Tue, Jun 7, 2011 at 9:20 AM, Jamison Fryman <jamison@puppetlabs.com>
wrote:
> My ask is this: I''m really interested in the various use cases of
nginx that are used by the community today that we can roll into this module.
If I was going to use a module like this I''d probably need a fallback
for directly-controlled vhost config for those vhosts which are rather
complex (which happens to be most :-) ).

Here''s a reverse caching proxy vhost of mine in front of SugarCRM
(itself on httpd): http://pastie.org/2069510
A Puppet master vhost: http://pastie.org/2069518
My nginx class (most of my classes look like this;
service+package+file): http://pastie.org/2069558

(I guess I have yet to subscribe to the goal that "As Puppet matures,
it expected that the file resource will be used less and less to
manage content, and instead native resources will be used to do
so."---I use file all over the place without it having becoming
cumbersome, and in fact find this easier than abstracting configs
behind native types.  My 2c!)

Eric

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I concur. Same problem applies to Apache vhosts - best intentions
never seem to cover all possible scenarios and its often good to have
a ''custom => template("foo/foo.conf")'' method for
allow custom stuff
to be added to a vhost entry - at least until each and all cases are
covered by native resources :-).

ken.

On Wed, Jun 15, 2011 at 12:29 AM, Eric Searcy <emsearcy@gmail.com>
wrote:
> On Tue, Jun 7, 2011 at 9:20 AM, Jamison Fryman
<jamison@puppetlabs.com> wrote:
>> My ask is this: I''m really interested in the various use cases
of nginx that are used by the community today that we can roll into this module.
>
> If I was going to use a module like this I''d probably need a
fallback
> for directly-controlled vhost config for those vhosts which are rather
> complex (which happens to be most :-) ).
>
> Here''s a reverse caching proxy vhost of mine in front of SugarCRM
> (itself on httpd): http://pastie.org/2069510
> A Puppet master vhost: http://pastie.org/2069518
> My nginx class (most of my classes look like this;
> service+package+file): http://pastie.org/2069558
>
> (I guess I have yet to subscribe to the goal that "As Puppet matures,
> it expected that the file resource will be used less and less to
> manage content, and instead native resources will be used to do
> so."---I use file all over the place without it having becoming
> cumbersome, and in fact find this easier than abstracting configs
> behind native types.  My 2c!)
>
> Eric
>
> --
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.