flynn23 wrote:
I know there are a lot of developer jockeys on this site. I'm working on a project where I'd like to use RoR. My background has been in Java development and I've been doing web stuff since the CGI was coined. But I've not set up a dev environment for RoR and I want to know what people use and what they find productive and efficient. I'll be doing this on Mac OSX, so any approaches on that platform are especially appreciated.

What editors are you using? How do you have your terms set up for optimal effectiveness? Are you using Mongrel or the OSX Apache? What's promotion from dev to production like? Do I have to install the whole XCode framework? Using MacPorts or is it a waste of time? Any other frameworks or tools that you find indispensable?

Also, is anyone using Spaces to keep the clutter from your dev environ separate from your "work" environ (email, irc, etc)? I'd almost like to boot into an image that was just for developing, do my thing, and then switch out. Just to keep those two worlds apart.

Sorry for the lack of response to this but I don't think my answers will help you much.

I did most of my programming for Tabjab in Vi. I didn't setup any Ruby specific stuff.

I used Apache, but not on OSX. I've gotten into the habit of running linux VMs on my Mac. I know it kind of defeats the purpose but some things are just easier that way. MacOSX is kind of a bastard UNIX.

I'm not sure if FastCGI works in OSX but I suspect it could be a bit of a pain. Are you using OSX as a server in production?! If so I think you have more money than sense. If you really hate linux run BSD.

Tabjab is still running in dev mode. I really should fix that but I haven't had time.

Generally speaking you should install XCode. I have a high opinion of MacPorts versus various other OSX package distribution systems. They seem to get the hard stuff right. I used to do development for Memestreams in OSX using MacPorts builds of Apache, Perl, and Postgresql.

As for separating worlds, there is always fast user switching.

RE: Ruby on Rails suggestions