|
I found this very useful when you need to sandwich a custom method that should be called when calling existing Rails method yet being able to still use it later on... Sorry, this sounds confusing... Read this: alias_method_bling http://errtheblog.com/post/1109
|
#
¿
Dec 6, 2007 05:39
|
|
|
|
| # ¿ Apr 26, 2024 06:06 |
|
|
Looks to me like Zed Shaw is an rear end in a top hat of massive proportions. Me? Oh, I'm just a nobody. But at least my ego can squeeze through doors.
|
|
#
¿
Jan 4, 2008 03:10
|
|
|
Never seen anything like that. Also you have shitloads of tests going on there. How long does it take to run and why so many?
|
|
#
¿
Jul 4, 2008 13:21
|
|
|
Well, for general api reference http://rails-doc.org is awesome. Hopefully it will be as good as php.net one day. There's pretty significant jump from 2.0 to 2.1 so old 1.* rails are almost irrelevant. http://weblog.rubyonrails.org/ is pretty alright if you want to follow wtf is happening (although most of the discussion is about Edge Rails that takes a bit to become stable). But for 2.1 changes check this out: http://weblog.rubyonrails.org/2008/6/10/free-rails-2-1-book
|
|
#
¿
Jul 8, 2008 03:10
|
|
|
NotShadowStar posted:Smallest I've done recently is a basic data collection form with a few fields. With templates it took about 15 minutes from 'rails fartlicker' to adding a Mongrel service to a production server. And if you used Passenger it would be even faster.
|
|
#
¿
Jun 29, 2009 13:31
|
|
|
CHRISTS FOR SALE posted:It's a great idea, especially in early stages of dev / beta releases you can live with a really basic admin views. It really doesn't take very long to implement, but if there was an option to skip it... Few things though: 1. Why not use it as an Engine? I don't see why you need to generate craploads of views and controllers in the app itself. Let user override defaults if he wishes though. 2. @models = Model.all(:table => RAILS_APP) How does that even work? I checked documentation just to be sure, but there's nothing like this there. Plus, wouldn't you just want AR models? 3. Tests. If there are no tests - it doesn't work.
|
|
#
¿
Nov 29, 2009 18:16
|
|
|
CHRISTS FOR SALE posted:I'll look into it. What I was trying to accomplish was something that would be easy to implement, a 3-step process that doesn't REQUIRE any dependent plugins. Maybe you're thinking about old 3rd party Engines. Rails 2.3 has that functionality built in: http://railscasts.com/episodes/149-rails-engines So instead of your 3-step process there's only one step: install gem.
|
|
#
¿
Dec 5, 2009 16:18
|
|
|
You don't know how much you hate Mongrel until you need to do a rolling restart on a cluster of 4 app servers with 4 processes on each while fighting with Monit so it doesn't kill newly created mongrel processes. Passenger is just a must now.
|
|
#
¿
Dec 29, 2009 14:27
|
|
|
Pardot posted:The gemcutter transition was really fast, like a month tops. Yet as a community we still haven't really embraced 1.9 Few things helped: Github gem hosting went tits-up and Github recommended Gemcutter as an alternative. Rubyforge was good for nothing other than being 'official' gem repository. Eventualy guy behind Rubyforge agreed that Gemcutter will server better for hosting gems. .. and then rubygems started to use Gemcutter as default.
|
|
#
¿
Jan 23, 2010 20:53
|
|
|
|
| # ¿ Apr 26, 2024 06:06 |
|
|
Try skipping :url thing completely. Rails sometimes is smart enough to figure out it:code:
|
|
#
¿
Apr 3, 2010 16:17
|
|