Comments for MadCode

Comment on upgrading hoptoad: uninitialized constant HoptoadNotifier::Catcher by Bruna Morrical

Bruna Morrical — Mon, 28 Nov 2011 03:37:14 +0000

Everybody keep saying look like I’m losing weight

Comment on Pow! Dead-easy rails development servers by Adeel Abbas

Adeel Abbas — Wed, 15 Jun 2011 07:55:59 +0000

Does it work Fine after all this procedure?? :S

Comment on quick tip: bunder, rails 2.3.8, and rspec by Tim

Tim — Thu, 31 Mar 2011 01:34:36 +0000

Thanks for this – worked a treat. I’m on 2.3.8 also.

Comment on quick tip: zsh and bundler by Alexey

Alexey — Wed, 22 Sep 2010 03:06:19 +0000

“rehash” or just open new zsh session in other terminal. no?

Comment on migrating a rails app from 2.x to 3.0 by Rails 3 Reading Material | Medium eXposure

Rails 3 Reading Material | Medium eXposure — Sun, 24 Jan 2010 07:54:14 +0000

[...] Migrating a Rails App from 2.x to 3.0 (01/17/10) — Another tutorial on steps needed to upgrade your Rails app. [...]

Comment on migrating a rails app from 2.x to 3.0 by matt

matt — Mon, 18 Jan 2010 14:25:57 +0000

My participation was pretty minor — a couple of hours on Sunday, and I didn’t do any bug-mashing to speak of — but the irc channel is a great resource. RailsBridge also did a good job of setting up ‘how do i get started?’ and ‘how do I participate?’ guides, so the most time could be spent on actually working rather than floundering.

Comment on migrating a rails app from 2.x to 3.0 by Derek Neighbors

Derek Neighbors — Mon, 18 Jan 2010 04:59:15 +0000

Great to step by step posted on this. So what was coolest or most irritating thing you found participating in RailsBridge?

Comment on running rake from cron by Raphaël

Raphaël — Sun, 15 Mar 2009 14:58:21 +0000

You can just put :

cd /myapp/path && RAILS_ENV=production /usr/local/bin/rake my:task

directly in your crontab

Comment on deploying php with capistrano by Johannes Fahrenkrug

Johannes Fahrenkrug — Tue, 23 Dec 2008 11:24:47 +0000

Hi Matt,

Thanks a lot, this was just what I needed. I've added a simple after_update task to the deploy namespace to remove the deploy.rb file after deployment so no one can access it through the web server (I know you could also solve this with a htaccess file or something, but this works too:)

task :after_update do # delete the capistrano file, so no one can see it run "rm #{release_path}/config/deploy.rb" end

Johannes