Installing Rails on a Mac Shouldn't Be As Hard As It Is
cabforward.com
Installing Rails on a Mac Shouldn't Be As Hard As It Is
1–10 of 100 posts
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#2Your first mistake is installing Rails. You're second mistake is attempting to do so on your development machine and not in a jail or vm.
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#3This is very helpful
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#4I am not sure installing a full stack web framework, a version control system, and automated deployment to public hosting should be _that_ easy. Learning how to install it all is very informative as to what is going on.
e.g. Deploying to Heroku is in fact very easy. Ok you have to mess around with ssh keys, but you don't want that to be automagic - you want to have some understanding of why what you are doing is secure, and why anyone else can't access your code.
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#5Yehuda Katz is working on a Mac app that sets Rails up on a Mac: http://www.kickstarter.com/projects/1397300529/railsapp
Also see this relevant (and relatively recent) update on the project: http://yehudakatz.com/2012/06/05/tokaido-status-update-imple...
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#6> Installing Rails on a Mac Shouldn't Be As Hard As It Is (cabforward.com)
1. Editorialized headline
2. It's easier than this article-- you don't have to install XCode: https://github.com/kennethreitz/osx-gcc-installer/
3. There are some smart folks working hard to make it easier: http://www.kickstarter.com/projects/1397300529/railsapp
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#7Maybe I'm coming at this from a different perspective as I've spent a number of years doing that whole "NINJAS BUILD FROM SRC.TAR" thing, but installing Rails under Mac has always been pretty straight forward. Get RVM > Get Ruby Version X > RubyGems > Rails > then fork off for databases if I want something fancy.
You are installing something that by it's nature requires a bit more understanding that just clicking on a .exe. Do you want to replace the default Ruby setup, which could potentially be used by something? Do you want to install new database servers? Do you want to modify Apache? Do you want to fiddle with SSH key gens? Do you want to have to delve in and change items of your .bash_profile? Do you trust an automated installer to be able to do it reliably on every single machine?
I'm not sure I'd have the confidence in something not going wrong and then sitting there with a half broken machine wondering what. At least this way at every step you can do the install > check & verify > confirm steps and make sure it's all business as normal.
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#8Your first mistake is installing Rails. You're second mistake is attempting to do so on your development machine and not in a jail or vm.
Not sure why you'd recommend installing Rails in a VM? It's a framework, not an environment.
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#9I am not sure installing a full stack web framework, a version control system, and automated deployment to public hosting should be _that_ easy. Learning how to install it all is very informative as to what is going on. e.g. Deploying to Heroku is in fact very easy. Ok you have to mess around with ssh keys, but you don't want that to be automagic - you want to have some understanding of why what you are doing is secu…
If you want it to replace php (or anything), it has to be as accessible as php for the same developer.
Until then, all the conversation about standards, best practices, and tutorials are far less accessible.
Re: Installing Rails on a Mac Shouldn't Be As Hard As It Is
#10Installing Rails and most everything else was simple for me. Getting mysql hooked up proved to be much more troublesome. Especially with MAMP installed already. I wish it would install in a contained package and not mess with anything else.