3 ms·
Similarly good experiences with setting up custom recipes that don't use the built in 'App' stack (which provides Rails, Node, and some others). I was able to
by skyebook 13y ago
Similarly good experiences with setting up custom recipes that don't use the built in 'App' stack (which provides Rails, Node, and some others).
I was able to go from the 'tinkering at 2am' level of ruby experience to making Chef do my bidding in setting up alternative apt-repos, deploying config files, etc in a day or two.
My one gripe, as with the rest of AWS, is that they seem more interested in MySQL than Postgres. The opsworks cookbook repo has an included mysql cookbook as well as a preconfigured "App" layer, nothing for Postgres besides forum responses to go the DIY route.
- miles932 13y agoOn the PostgreSQL note, here's a whitepaper I helped with that enumerates best practices for it on AWS: http://media.amazonwebservices.com/AWS_RDBMS_PostgreSQL.pdf http://media.amazonwebservices.com/AWS_RDBMS_PostgreSQL.pdf
- skyebook 13y agoPlease allow me to give an emphatic THANK YOU for writing that... I've gone to it more than once in the short while its been floating around and it has generally been helpful in either giving me some conviction in what I'm doing or righting my ways. Unfortunately, and this drives me nuts about so many PaaS offerings, maintaining a database at scale is a really niche thing that people devote tons of time to.. Arguably many times more difficult than keeping a bunch of app servers up.. I would love to see more hosted offerings along the line of EnterpriseDB and Heroku's Postgres service. Thanks again for the awesome resource :)