<div>
Allow me to be pedantic:</div><div><br></div><div>• You have a cron job that regularly checks out the vagrant/puppet git repo and runs the puppet (?? which one?) executable on it.</div><div>• Your deployment server has a 'vagrant' user that has sudo privileges</div><div><br></div><div>Would you be willing to send me your bootstrap script? I think more than anything that's what will help all the pieces fall in place in my mind. I'll probably need to write my own, but to have yours to work off of (I learn by studying examples) would be very helpful.</div><div><br></div><div>Not using puppet for deployment makes sense. I have the puppet script, for development purposes, doing a git checkout of the application, but for staging/production purposes I would set up all the services, directories, etc. so they're ready to go, but would require a 'cap deploy' (of some sort) to make the application go.</div><div><br></div><div>Thanks,</div><div>Paul.</div>
<div><div><br></div><div>-- </div><div>Paul Doerwald</div><div>Chancellor, Liquid Media Inc.</div><div>902-412-2492</div><div><br></div></div>
<p style="color: #A0A0A8;">On Monday, 22 April, 2013 at 10:59 AM, David Salgado wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div dir="ltr"><div>We use the same puppet code on vagrant VMs and Rackspace/EC2 VMs.</div><div><br></div><div>The server periodically checks the puppet code out of the git repository and applies it, so that all servers keep themselves up to date.</div>
<div><br></div><div>To conditionally apply puppet code that should/shouldn't be applied on vagrant VMs we set a global variable in Puppet like this;</div><div>
<br></div><div> $vagrant_dev_vm = inline_template('<%= FileTest.exists?(\'/tmp/vagrant-puppet\') ? \'true\' : \'false\' %>')<br></div><div><br>
</div><div style="">i.e. if the directory /tmp/vagrant-puppet exists, we're a Vagrant VM (so don't do whatever stuff should only happen in the staging/production environments).</div><div style="">
<br></div><div style="">We don't use Puppet for deployment though - just for keeping the servers in the correct state to be deployed to. Having said that, it would be pretty simple to tweak our Puppet code so that deployments happened automagically too. There's also a Puppet-based deployment tool called Puppi, that might be worth looking at.</div>
<div style=""><br></div><div style="">To go from a clean hosted VM to a deployed server we use a bootstrap task that ssh's onto the box and sets up just enough stuff to get puppet to run, then puppet takes it from there. We also use the fog gem to automate the setup of the clean VM in the first place.</div>
<div style=""><br></div><div style="">Hope this helps</div><div style=""><br></div><div style="">David</div><div style=""><br></div><div>
<br><div>On 22 April 2013 14:39, Paul Doerwald <span dir="ltr"><<a href="mailto:paul@liquidmedia.ca" target="_blank">paul@liquidmedia.ca</a>></span> wrote:<br><blockquote type="cite"><div>
<div>Hola El Rug,
</div><div><br></div><div>I noticed someone mention puppet in a recent message and it occurred to me that I could ask the LRUG list for advice. </div><div><br></div><div>I am new to Vagrant and Puppet. I have a brute force but effective script that can create a dev environment very nicely. I would like to use the same script (or more accurately, a variation of it, because right now the script is a bit stupid) to deploy the staging and production versions of the application on a Linode computer.</div>
<div><br></div><div>A bit more context on my problem:</div><div><br></div><div>• The application will never grow bigger than a single computer, so auto-deployment/build (basically the big win that Puppet and Chef bring you) are not important. Repeatability of deploy is the big value.</div>
<div>• I don't mind a manual process (i.e. running an executable on the deployment server whenever I update the Puppet script).</div><div>• Ordinarily this kind of investment for a single application isn't worthwhile, but most of my work (all client work) fits the same profile (more or less) and so I do intend to leverage this investment in making repeatable deploys for all my other clients, present and future.</div>
<div>• My Puppet config (and Vagrant, for that matter) is in a Github repo, separate from the application.</div><div><br></div><div>Does anyone have experience going from Vagrant/Puppet to Linode(or any VPS)/Puppet, particularly for a single-server environment?</div>
<div><br></div><div>If not, does anyone with Puppet experience have any advice for how I might tackle the Linode portion of the problem? </div>
<div><div><br></div><div>I'm looking for a conceptual orientation to how I should solve the problem. I'm sure I can figure out the details. All the advice on the Internet is in the context of a multi-server setup, and it's never coming from a Vagrant perspective.</div>
<div><br></div><div>Thanks for your thoughts!</div><span><font color="#888888"><div>Paul.</div><div><br></div><div><br></div><div>-- </div><div>Paul Doerwald</div><div>Chancellor, Liquid Media Inc.</div><div><a href="tel:902-412-2492" value="+19024122492" target="_blank">902-412-2492</a></div>
<div><br></div></font></span></div>
<br>_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
<a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></div></blockquote></div><br></div></div>
</div><div><div>_______________________________________________</div><div>Chat mailing list</div><div><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a></div><div><a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>