Git: restoring accidentaly deleted files

To view a list of deleted files:

git ls-files --deleted

To restore a deleted file (assuming the D is not yet commited)

git checkout where/the/file/was.ext

custom assert_select_rjs matcher

Background:
I wanted to test rjs redirection:


Problem:
ActionController::Assertions::SelectorAssertions#assert_select_rjs don't know about :redirect_to

Solution:
I don't know if this is the right solution but I added this at the end of my test_helper.rb then I can assert by :redirect_to now

Application Controller

The file application.rb had just been officially renamed to application_controller.rb; and the special case in the code for checking it removed. I'm not even OC but this was also bothering me since I used rails.

The commit: fcce1f1

reverse_sql_order

I just found this while browsing through AR Base's source code. It seems very useful.

"Only get, head, post, put, and delete requests are allowed." Ruby on Rails error

Only get, head, post, put, and delete requests are allowed.

If you get this while/after editing your routes, then you'll need to restart your local server. Thanks to this guy.

Using custom column type in Rails migrations

It seems if the type you gave to a column definition in a migration is not listed in native_database_types, Rails will just use what you gave it.

Therefore this will work:

Rubyforge gem problem

Problem:

starting the server and you get:

 can't activate rubyforge (= 0.4.5), already activated rubyforge-1.0.0] (Gem::Exception)

Solution:
remove old versions of rubyforge gem

jorrel@helen ~ $ sudo gem uninstall rubyforge

Select gem to uninstall:
1. rubyforge-0.4.4
2. rubyforge-0.4.5
3. rubyforge-1.0.0
4. All versions
> 1
Successfully uninstalled rubyforge-0.4.4
jorrel@helen ~ $ sudo gem uninstall rubyforge

Select gem to uninstall:
1. rubyforge-0.4.5
2. rubyforge-1.0.0
3. All versions
> 1
Successfully uninstalled rubyforge-0.4.5
jorrel@helen ~ $ gem list | grep rubyforge
rubyforge (1.0.0)

mod_rails + edge rails

Based on a recent conversation at phusion passenger google group, there is a bug wherein mod_rails fails to start its spawner for an application that uses edge rails.

Basically, you'll get this error (complaining about a failed 'to_constant_name' somewhere):

  Framework that failed to load:
  Vendor directory: /path/to/vendor/rails
Error message:
  Anonymous modules have no name to be referenced by
Exception class:
  ArgumentError

More info about the bug can be found in the bug report filed by hongli


update: This seems to be fixed in edge rails + git passenger (though I havn't tried yet), as hongli's comment below says.

mod_rails + rails 2.0

I you encounter a "500 Internal Server Error" after setting up mod_rails in a recent (rails 2.0) application, you need to delete 'public/.htaccess'.