Having been a Rails developer I don't have much trouble getting Rails up and going on a system. However I do have several friends who seem to have no end of trouble getting theirs setup working reliably. Given they are not full time developers, but they complain about how hard it is to get everything configured so I can see how useful something like this can be for many people looking to try out Rails.
Kickstarter: rails.app
41–50 of 175 posts
Re: Kickstarter: rails.app
#42Gimme one .app and a directory structure I can just throw into /Applications (and later throw away if my experiments come to naught), gimme a nice control panel to stop and start Rails. Let me get it up and running on my system without hassling with the Terminal. Because I really really avoid the Terminal as much as possible.
pledges ten bucks
Re: Kickstarter: rails.app
#43Seems like this is connected to rails 4 release: sidebar: "and your input will guarantee that Rails 4 is as great for beginners as it is for experienced developers."
Re: Kickstarter: rails.app
#44I'm interested in whatever Yehuda Katz comes up with, but I've been a Rails dev at a Mac shop since 2007? and I have never been too frustrated by getting Rails running. Does anyone here have specific problems? From my experience, it really has been a matter of "gem update --system; gem install rails".
> "gem update --system; gem install rails" That'll throw a permissions error on a default OS X install-- and your Rails newbie will definitely not know that that means "you should really use rvm". With that said-- a shell script that installs homebrew, git, rvm, the latest ruby, the latest rails, and a handful of useful gems, then drops you right into a shell of you brand spankin' new Rails (and Heroku!) project seem…
Re: Kickstarter: rails.app
#45I'm interested in whatever Yehuda Katz comes up with, but I've been a Rails dev at a Mac shop since 2007? and I have never been too frustrated by getting Rails running. Does anyone here have specific problems? From my experience, it really has been a matter of "gem update --system; gem install rails".
In fact, it was so messed up, it motivated me to go out and buy a new Macbook (I needed a new computer anyway, but it provided a major impetus to go out and get one).
And that's just me. Even worse is the fact that I work on a lot of Rails projects with a designer who lives in Montreal, which is a good six hour drive from where I live. I've helped him get Rails set up on his computer, but it has not been easy - far from it. As a non-techie his computer is prone to all sorts of weird shit, he hates the CLI, he needs to be walked through, line-by-line, any situation involving some weird gem dependency nonsense - it's a horrible waste of my time. Imagine trying to debug someone's effed-up gem environment via a laggy screen-sharing connection while you're on deadline - it's awful!
To sum it up: this is a project worth supporting and I'm going to support it as soon as I click the 'reply' button on this comment form.
Re: Kickstarter: rails.app
#463 step process: Step 1: Download the "Command line tools for Xcode" here https://developer.apple.com/downloads/index.action Step 2: Install homebrew with this command /usr/bin/ruby -e "$(/usr/bin/curl -fksSL https://raw.github.com/mxcl/homebrew/master/Library/Contribu... Step 3: gem install rails
Yah, rather then funding a project to make Rails easier to install on OSX (because it's not with the plethora information guides and bootstrap scripts), why not tackle real problems like concurrency and websockets in Rails.
Lowering the Rails entry bar is a good thing, making things simpler is a sign of maturity for a product. To address your bit about concurrency and websockets in Rails, people are working on the issue, see the talks given by Ilya Grigorik for example, concurrency will be coming to Rails at some point. And so will the integration with client-side framworks like Backbone or Ember. It just takes time.
Re: Kickstarter: rails.app
#47I feel like this is overkill. I have been using RailsReady ( https://github.com/joshfng/railsready ) to setup several Mac and Ubuntu boxes and it has never been more than one click.
Re: Kickstarter: rails.app
#483 step process: Step 1: Download the "Command line tools for Xcode" here https://developer.apple.com/downloads/index.action Step 2: Install homebrew with this command /usr/bin/ruby -e "$(/usr/bin/curl -fksSL https://raw.github.com/mxcl/homebrew/master/Library/Contribu... Step 3: gem install rails
brew install rbenv
brew install ruby-build
Copy the line it gives you to your shell's rc file and source it/open a new term: rbenv install 1.9.3-p125
rbenv global 1.9.3-p125
gem update --system
gem install rails
gem install bundler # optional, recommended
When a new version of Ruby comes out: brew update
brew upgrade
Then just rbenv install and rbenv global it.Re: Kickstarter: rails.app
#493 step process: Step 1: Download the "Command line tools for Xcode" here https://developer.apple.com/downloads/index.action Step 2: Install homebrew with this command /usr/bin/ruby -e "$(/usr/bin/curl -fksSL https://raw.github.com/mxcl/homebrew/master/Library/Contribu... Step 3: gem install rails
Re: Kickstarter: rails.app
#50Seems like this is connected to rails 4 release: sidebar: "and your input will guarantee that Rails 4 is as great for beginners as it is for experienced developers."
The main link to Rails 4 is that we've announced that Rails 4 will drop Ruby 1.8.7 support, which means that some sort of install will be mandatory on OSX beginning with Rails 4.