Problem
You would like to test your factory_girl factories in the rails test console, but you get an error when you try to use an existing factory.
Solution
rails c testrequire 'absolute_path/to/your/factories.rb't=Factory.create(:existing_factory_name)Problem
When you try to create a new Rails 3.0.x application, and try to use the ‘mysql2’ gem in your Gemfile without specifying a version you get the following warnings:
WARNING: This version of mysql2 (0.3.2) doesn't ship with the ActiveRecord adapter bundled anymore as it's now part of Rails 3.1
WARNING: Please use the 0.2.x releases if you plan on using it in Rails <= 3.0.x
Solution
Specify the latest version of mysql2 that is compatible with the Rails 3.0.x versions as in:
gem 'mysql2', "~> 0.2.7"
Problem
When you try to run the console rails c in a new Rails 3.0.7 application, in Mandriva 2011 64bit, and when you use rvm, you get the following error:
no such file to load -- readline (LoadError)
Solution
Similar to an earlier post here, the solution is as follows with the new requirements described
It’s quite like likely that the readline libraries are missing from your installation. To find out which ones go to the directory that the error is indicating (ie):
cd ~/.rvm/src/ruby-1.9..2-head
and then to the following:
cd ext/readline
then run the following:
ruby extconf.rb
If you get something like:
checking for readline/readline.h... no
checking for editline/readline.h... no
then you are probably missing the neccessary header files for readline.
so install them in your system (ie in Mandriva):
sudo urpmi lib64readline-dev,
When the package is installed successfully run the following again:
ruby extconf.rb
make
sudo make install
You should now be able to go back to your project and run rails c with no errors.
Problem
You are trying to set up gitolite access through gitweb but the gitweb page, shows ‘no projects avaiable’ even though you have repositories available.
Solution
Try to follow the guide here.
Some of tthe most important steps for having the right access permissions are:
$ sudo usermod -a -G gitolite www-data$ sudo vi /etc/gitweb.conf
$projectroot ="/var/lib/gitolite/repositories";
$projects_list="/var/lib/gitolite/projects.list";$ sudo chmod g+r /var/lib/gitolite/projects.list
$ sudo chmod -R g+rx /var/lib/gitolite/repositories$REPO_UMASK = 0027;exec chpst -ugitdaemon:gitoliteProblem
When trying to use cucumber in a new rails 3.0.7 application you get the following error when running rake cucumber for the first time:
uninitialized constant Capybara (NameError)
Solution
As cucumber is moving to using capybara instead of webrat as default, if you follow the instructions in the Rspec book for setting up you would get the above error.
What you would need to do is to replace webrat with capybara.
You can do that by commenting out /removing webrat from your Gemfile and then adding the following:
gem 'capybara'
gem 'database_cleaner'
Problem
You are trying to use rspec with Ruby on Rails 2.3.10, but although you install the rspec and rspec-rails gems you get the following error when you try to run script/generate rspec
Couldn't find 'rspec' generator
It turns out that there is a problem with the versions used, so by following the instructions for Rails >= 2.3.10 from here, you should be able to install the plugins and use rspec:
ruby script/plugin install git://github.com/dchelimsky/rspec.git -r 'refs/tags/1.3.1'
ruby script/plugin install git://github.com/dchelimsky/rspec-rails.git -r 'refs/tags/1.3.3'
ruby script/generate rspec
where the last tag (1.3.3) should be the latest tag for each gem.
*** NOTE *** If you get an error like :
You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.map (NoMethodError)
uncomment the following line (line 11) from features/support/env.rb:
require 'cucumber/rails/rspec'
and run rake cucumber again.
Problem
You would like to have colours in the output of your capistrano tasks similar to the ones in cucumber, indicating errors (red) or completed actions(green).
Solution
Install the capistrano_colours gem that can be found here.
sudo gem install capistrano_colors
Problem
After the announcements in the previous posts about the security vulnerabilities in Rails 3.0.3, you would like to update your application and deploy with the latest 3.0.4 version.
Solution
gem 'rails', '3.0.3'gem 'rails', '3.0.4'bundle update railsgit statusgit rm name_of_3.0.3_gemgit add vendor/cachegit commit vendor/cache -m 'upgrade to rails 3.0.4'git commit Gemfile Gemfile.lock -m 'update Gemfiles to use 3.0.4'You have modified your Gemfile in development but did not check the resulting snapshot (Gemfile.lock) into version controlgit pushcap deploySecurity announcement about potential SQL injection with limit().
Full details here.
Versions affected 3.0.0 to 3.0.3.
Security announcement about filtering problems on case insensitive filesystems.
Full details here
Versions affected 3.0.0 to 3.0.3