gdp's Comments

Union Station : Deployment Best Practices with Engine Yard and Bundler 1.0

Thu, 23 Sep 2010 05:05:50 +0000

> Everybody keeps telling me Bundler is awesome, but to tell you the truth > I never had any problems with gem dependencies in the past. It wasn't like > unpacking gems into an app and using a few select gems on the server is > actually difficult. There are definitely some people (like you) with that experience. There are also a lot of people with the opposite experience. Unfortunately, dependency issues are silent killers--they pop up out of nowhere and kill you for days while you try to understand what gem that happened to exist on production took down your app. This is no exaggeration; Ruby forums are littered with the corpses of people who thought everything was fine until an errant gem install rack on a developer machine or on production inadvertently took down their app. > Furthermore: now with Bundler my deployments *are* actually more > difficult all of a sudden. Even though I have the rspec gem in the development > "group" (why is this not named environment?) People use groups for things other than environments. For instance, some people put all of their cucumber dependencies in a :cucumber group, but don't necessarily have a cucumber environment. In Rails, we made group == environment by default. > when I deploy on production Bundler still wants to install it. Why oh why? > No documentation will tell me. If you do nothing but run `bundle install` on production, bundler will install all groups. The simplest way to deploy bundler, as documented at http://gembundler.com/deploying.html (and also on the front page of gembundler.com) is to put require "bundler/capistrano" in your capistrano file. This task defaults to skipping the development and test groups, and allows you to configure it to skip other groups if you wish. It also uses `bundle install --deployment`, which installs the gems to a local path in your application, dealing with a number of common issues involving passenger and unicorn. > You seem to be using some magic to get this to work, but alas no actual > light on this subject. Is there a black craft to this? Engine Yard uses bundle install --deployment --without development test, which is the same thing that the bundler/capistrano task does for you. > If you ask me, Bundler is like using a state of the art NASA kevlar sheet > instead of a band-aid for a minor cut.

Union Station : Rails and Merb Merge: ORM Agnosticism (Part 5 of 6)

Tue, 23 Feb 2010 19:52:47 +0000

Fixed! Thanks for reporting that :)

Union Station : Rails 3 Beta is Out -- A Retrospective

Fri, 5 Feb 2010 17:29:42 +0000

Yeah. Use Post.all when you expect to get back an Array; use Post.scoped if you want a relation.

Union Station : Rails and Merb Merge: Rails Core (Part 4 of 6)

Fri, 22 Jan 2010 21:06:13 +0000

Good catch. Both typos are fixed :)

Union Station : Rails and Merb Merge: Plugin API (Part 3 of 6)

Wed, 13 Jan 2010 06:16:26 +0000

Then you believe incorrectly ;) The benchmarks are located at http://github.com/wycats/rails-simple-benches and can be run by checking the repo out into the actionpack dir in Rails. It includes the full cost of a Rack request, without the network overhead (important, but not a cost that Rails is responsible for).

Union Station : Rails and Merb Merge: Plugin API (Part 3 of 6)

Wed, 13 Jan 2010 06:15:16 +0000

Ha. I think I probably would have pointed you to those same places. Rails 3 exposes a Railtie class that any plugin can subclass and have access to initialization, middleware, configuration, etc. We're still working on the right workflow for routing stuff (because there are multiple "correct" solutions), and we'll have stuff for you soon.

Union Station : Rails and Merb Merge: Plugin API (Part 3 of 6)

Wed, 13 Jan 2010 06:12:51 +0000

Yeah. Leftovers from the syntax highlighting fail. Looking into fixing it.

Union Station : Rails and Merb Merge: Plugin API (Part 3 of 6)

Mon, 11 Jan 2010 21:02:04 +0000

Should be fixed. I believe it also won't recur :)

Union Station : Rails and Merb Merge: Performance (Part 2 of 6)

Tue, 29 Dec 2009 22:01:41 +0000

Thanks for pointing it out. Seems to be a bug with our syntax highlighting. I'll see if I can get it taken care of :/

Union Station : Rails and Merb Merge: The Anniversary (Part 1 of 6)

Thu, 24 Dec 2009 17:30:27 +0000

Plugins should individually pull in the parts of ActiveSupport that *they* need. You'll only need to pull in parts of ActiveSupport that you're explicitly using -- I agree that otherwise the idea would be untenable.

Union Station : Rails and Merb Merge: The Anniversary (Part 1 of 6)

Thu, 24 Dec 2009 05:42:26 +0000

Working on it :P

Union Station : Your Pages Will Load Faster with Rails!

Wed, 16 Dec 2009 01:22:50 +0000

@dan we have actually been looking into this... one difficulty involves the way Ruby layouts typically work -- they essentially require rendering the template first, and then inserting it into the template. If the user guaranteed that no state would be set in subviews and then expected to be available in the layout, we could do additional tricks. Expect to hear more about this after 3.0.

Union Station : Your Pages Will Load Faster with Rails!

Tue, 15 Dec 2009 23:02:48 +0000

I'd love to see some examples of other frameworks that provide asset hosts via a single configuration option, timestamped query string, and automatic concatenation of collections of JavaScript and CSS files. Again, I want to see this provided as part of the normal helpers, and not require changing a bunch of locations to opt into asset hosts, for instance.

Union Station : Your Pages Will Load Faster with Rails!

Tue, 15 Dec 2009 22:07:09 +0000

Good catch. You should be gzipping CSS

Union Station : Your Pages Will Load Faster with Rails!

Tue, 15 Dec 2009 21:45:12 +0000

Yeah my bad. I'll correct the post.

Union Station : Your Pages Will Load Faster with Rails!

Tue, 15 Dec 2009 21:36:58 +0000

Good catch. You should be gzipping CSS, JS and HTML, not images.

Union Station : Your Pages Will Load Faster with Rails!

Tue, 15 Dec 2009 21:24:03 +0000

Why not?

Union Station : Your Pages Will Load Faster with Rails!

Tue, 15 Dec 2009 19:37:34 +0000

Yep! Yet another thing Rails does for you. I plan to have more details on additional Rails help next week :)

Union Station : My Five Favorite Things About Rails 3

Wed, 2 Sep 2009 02:39:59 +0000

Mid 2010 would be extremely pessimistic for a beta.

Union Station : My Five Favorite Things About Rails 3

Thu, 20 Aug 2009 05:05:57 +0000

Not necessary. HTML5 validators won't complain, and the HTML5 doctype will work on all browsers. I think people have just been burned so hard by browsers that they're afraid to even THINK that this stuff will work. But it does.