61–70 of 175 posts
What about on a virtual private server like at linode? Then one doesn't necessarily have to shell out for a Mac to run osx. I would be much more interested in that.
I'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".
Generally speaking, you now need a compiler. If not to install something other than a quite old system ruby, then to install common gems like nokogiri.
XCode seems to change significantly every release. Not long ago, you had to download it, or get it from your system CDs. Then you had to buy it from the app-store. Then you got it for free from the app-store. Then you got the installer for free from the app-store, and had to run the installer. And today I think you get the installer, which you run, and then you go through a series of menus to get to "install command line tools" (like gcc).
Once gcc is there, then you need a ruby. There's RVM and rbenv. Those need to be found, installed (by running a curl command piped through bash), and then a ruby needs to be installed. I use RVM, which is easy enough for me, and it does install bundler by default (which is good).
Once you have a modern ruby, you probably want a database other than sqlite. For that, you usually need homebrew. Again, install homebrew, and then have homebrew install postgresql/mysql.
At this point you are almost ready to install the rails gem.
Oddly, a lot of the newer complexity has less to do with Rails, and has more to do with the Ruby ecosystem getting both older and more complex at the same time.
Every time I help a new developer get started with the rails environment, I too am amazed at how much has changed since I setup my own laptop one year ago.
I have several problems with this. The first, and most important, is here: http://xkcd.com/927/ The second is personal, so please take it with a grain of salt. I pointed out that Yehuda's Bundler gem has an automated condescension feature; if you try to use it without saying 'source :rubygems,' it heckles you and mockingly asks you 'did you mean to say source :rubygems? if so please go back and type it in.' this is p…
I have several problems with this. The first, and most important, is here: http://xkcd.com/927/ The second is personal, so please take it with a grain of salt. I pointed out that Yehuda's Bundler gem has an automated condescension feature; if you try to use it without saying 'source :rubygems,' it heckles you and mockingly asks you 'did you mean to say source :rubygems? if so please go back and type it in.' this is p…
Some other good ones:
I have several problems with this. The first, and most important, is here: http://xkcd.com/927/ The second is personal, so please take it with a grain of salt. I pointed out that Yehuda's Bundler gem has an automated condescension feature; if you try to use it without saying 'source :rubygems,' it heckles you and mockingly asks you 'did you mean to say source :rubygems? if so please go back and type it in.' this is p…
Do you mind going into some details about why the Bundler gem was mocking you? I'm a Python dev and only know rudimentary rails/ruby.
edit: The RubyRouges podcast has a great episode with the maintainer of Bundler where a lot of the difficulties with Bundler are discussed in depth. That's the "talk" I was referring too.
I have several problems with this. The first, and most important, is here: http://xkcd.com/927/ The second is personal, so please take it with a grain of salt. I pointed out that Yehuda's Bundler gem has an automated condescension feature; if you try to use it without saying 'source :rubygems,' it heckles you and mockingly asks you 'did you mean to say source :rubygems? if so please go back and type it in.' this is p…
Do you mind going into some details about why the Bundler gem was mocking you? I'm a Python dev and only know rudimentary rails/ruby.
the idea in Ruby, and especially in Rails, is that if you know what the default is which most people are going to expect or try, you should support it. to say "we know you thought source :rubygems was the default, but it's not, you have to type it explicitly" is a little un-Ruby and a whole bunch un-Rails.
I have several problems with this. The first, and most important, is here: http://xkcd.com/927/ The second is personal, so please take it with a grain of salt. I pointed out that Yehuda's Bundler gem has an automated condescension feature; if you try to use it without saying 'source :rubygems,' it heckles you and mockingly asks you 'did you mean to say source :rubygems? if so please go back and type it in.' this is p…
This seemed a little odd to me as well, but mostly because I haven't been a noob for a long time and so am out of touch with that feeling of "this is hard" when it comes to installing rails. I don't think that installing rails got any harder relative to where it was in the 1.0 days. vanilla rails locked to one version with globally-installed gems is just as easy as it ever was, so I don't know if its quite fair to sa…
Earlier quoted context omitted.
Do you mind going into some details about why the Bundler gem was mocking you? I'm a Python dev and only know rudimentary rails/ruby.
In your Gemfile Bundler requires you to tell it where to lookup for gems. For 99.99% of people that is going to be rubygems.org, but it doesn't have to be. There has been talk about making this the default and then allowing someone to turn it off. edit: The RubyRouges podcast has a great episode with the maintainer of Bundler where a lot of the difficulties with Bundler are discussed in depth. That's the "talk" I was…
I say at best because obviously in my case I did not see a whole lot of debate. the GitHub issue for it is likewise extremely not-discussion-y. wherever the discussion for this incredibly controversial idea is taking place, I haven't seen it.