Hi John,
Am 09.09.2013 15:39, schrieb jcbollinger:
On Monday, September 9, 2013 1:52:43 AM UTC-5, Stepan Seycek wrote:
Hi John,
thanks for your reply. Unfortunately that does not solve my actual
problem. I want to avoid maintaining multiple vhost entries inside
one file.
My suggestion accomplishes that. Following Puppet best practices and
autoloader requirements, each vhost class would go into a separate file.
Instead I want to be able to add a vhost by simply adding one file
dedicated to that vhost to a directory.
You didn't say the part before.
This would allow me to easily integrate puppet with a tool that
rolls out whole application stacks including the vhosts.
It can be done -- with 'import', even -- but most of the options for
such a setup are poor practice. To suggest a good alternative, I
would like to better understand your planned usage. Will you be using
Puppet in agent / master mode, or standalone mode? Are you looking
for one-time deployment, or continuing vhost management? Will you
ever have to support multiple servers with different vhosts? With
overlapping vhosts? Do you need to provide for removing unwanted
vhosts? Would it be an unacceptable burden to run a second tool after
the one that produces the vhost information, before it is ready for
Puppet?
Puppet runs in master/agent mode.
Puppet shall be used for continuous vhost management.
There will be multiple servers providing reverse proxy services with
apache httpd vhosts (different vhosts on different servers).
Removal of vhosts is definitely a requirement for the undeployment of an
application stack.
An additional tool processing the configuration for puppet is no problem.
I know I could maintain the information about active vhosts in my
roll-out tool and when submitting to puppet generate a class file that
would contain all active vhost declarations and would declare removals
for those that have been active before and are not among the active ones
any more. However, as mentioned before, I would prefer to generate a
file for every to-be-added vhost and every to-be-removed vhost.
Regards,
Stepan
John
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
