Re:Setting up PostgreSQL for Ruby on Rails development on OS X
by pilif on Tuesday May 31, 2011 @10:36AM
(#2602746)
Why not just use the one-click-installer? http://www.enterprisedb.com/products-services-training/pgdow... it neatly creates a system user if needed, modifies sysctl.conf (for shmmax) and installs a few items in the Application folder for quickly starting and stopping the server.
Re:Setting up PostgreSQL for Ruby on Rails development on OS X
by telemachos on Tuesday May 31, 2011 @10:40AM
(#2602764)
The article mentions the Postgres installer, but mostly assumes the reader uses Homebrew (MacPorts is mentioned at the bottom as well). I have no way to get real numbers, but given Homebrew's overall popularity on Github, I suspect that assumption is a good bet for a very large number of Rails developers on OSX.
Once you choose a package manager, it tends to be easier to always use that, rather than use one-off binary installers. (In fact, the one-off binary installers can lead to known permissions problems when it comes to Homebrew specifically.)
Note for both pro- and anti-Mac folks. I'm simply trying to show how the grandparent post is relevant - why it's here. I'm not stating an opinion one way or the other on anything else.
Re:Setting up PostgreSQL for Ruby on Rails development on OS X
by telemachos on Tuesday May 31, 2011 @10:47AM
(#2602784)
It looks like a great overview. One thought: you might mention Lunchy (https://github.com/mperham/lunchy) as a nice Ruby-friendly way to manage the not-so-nice, not-so-friendly launchctl business.
Re:Setting up PostgreSQL for Ruby on Rails development on OS X
by roelbondoc on Tuesday May 31, 2011 @01:33PM
(#2603543)
I agree. Developing on Ubuntu on a VM has been a great experience for me so far. It seems much less painful to develop on a platform that is similar to where you will be deploying.
Once you choose a package manager, it tends to be easier to always use that, rather than use one-off binary installers. (In fact, the one-off binary installers can lead to known permissions problems when it comes to Homebrew specifically.)
I'm pretty sure that Technomancy is indirectly making a point about Apple's lack of a package manager. Something like this, I'm guessing: http://teddziuba.com/2011/03/osx-unsuitable-web-development.... (the part about package management, that is).
Note for both pro- and anti-Mac folks. I'm simply trying to show how the grandparent post is relevant - why it's here. I'm not stating an opinion one way or the other on anything else.