comment on

ansible and vagrant are pretty nice.

Lots of hardcore operations folks will tell you to go with Chef or Puppet because of flexibility/robustness, but it all depends on your infrastructure needs. Chef has A LOT of documentation on deploying things on AWS, and pre-canned recipes for Rails, Scala, etc. type apps, and Puppet has some automation solutions for things like RDP (Windows), though I am not sure if Chef can deal with that, but I digress.

If you want dead simple setup and just need quick, basic deployment automation, check out ansible. If you are starting from the ground up, check out Chef + Berkshelf. You'll want that kind of control if you're going to scale fast and have many types of machines that need provisioning/nannying, it's just very involved.

Three thousand years of beautiful tradition, from Moses to Sandy Koufax, you're god damn right I'm living in the fucking past

In reply to Re: Experiences with deployment solutions by stonecolddevin
in thread Experiences with deployment solutions by McA

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks