News for hackers. Stuff that matters.
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.)

Re:Setting up PostgreSQL for Ruby on Rails development on OS X by technomancy on Tuesday May 31, 2011 @12:36PM (#2603263)
Re:Setting up PostgreSQL for Ruby on Rails development on OS X by wlll on Tuesday May 31, 2011 @12:41PM (#2603296)
Seems irrelevant…
Re:Setting up PostgreSQL for Ruby on Rails development on OS X by telemachos on Wednesday June 01, 2011 @01:03PM (#2608181)
Read the whole post in the link (or skim it at least).

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.

Re:Setting up PostgreSQL for Ruby on Rails development on OS X by listrophy on Tuesday May 31, 2011 @09:47AM (#2602537)
Great guide, even if one completely ignores the RoR part.
Re:Setting up PostgreSQL for Ruby on Rails development on OS X by wlll on Tuesday May 31, 2011 @10:21AM (#2602682)
Thanks for the comment, that's great to hear!
Re:Setting up PostgreSQL for Ruby on Rails development on OS X by wlll on Tuesday May 31, 2011 @08:56AM (#2602344)
If anyone has any questions about the process, or gets stuck leave them as comments on my post, I'll help out where I can.
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 chopsueyar on Tuesday May 31, 2011 @12:59PM (#2603365)
Virtual machine!!!
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.
Re:Setting up PostgreSQL for Ruby on Rails development on OS X by chopsueyar on Tuesday May 31, 2011 @02:40PM (#2603863)
When I first read the headline, I immediately wondered who was deploying to a production OS X server with PostgreSQL.
Re:Setting up PostgreSQL for Ruby on Rails development on OS X by techscruggs on Tuesday May 31, 2011 @10:09AM (#2602646)
With the advent of Homebrew, why would manually compile from source for your local dev environment?
Re:Setting up PostgreSQL for Ruby on Rails development on OS X by wlll on Tuesday May 31, 2011 @10:21AM (#2602677)
My article suggests and assumes you are using Homebrew.
Re:Setting up PostgreSQL for Ruby on Rails development on OS X by techscruggs on Tuesday May 31, 2011 @04:25PM (#2604370)
Crap, my apologies, I obviously skimmed that article as opposed to reading it. mea culpa