Am Mittwoch, 27. Februar 2013 18:26:12 UTC+1 schrieb Brian Mathis: > > > A more typical workflow would be to keep all your production files > within /etc/puppet on the puppet master, with those checked out from a > production branch in your CVS server. On your development machine, > you use a separate checkout from a separate branch, and when you're > done you push into the production branch, then update to that release > on your production server. ...
For my small setup, I wanted to keep things a bit simpler, and not set up a second, test, puppet master, but edit the files in the development environment of the master directly, test by 'kicking' the test node, and if things work, commit and later push the committed files to the production environment. For anything larger than, say one server and a test and production node, a more elaborate setup would certainly make sense. thanks, Roman -- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
