bundle config set –local path ‘vendor/cache’ generally fixes it as that is the more common problem. Basically, your bundler path configuration is messed up. See their documentation (first paragraph) for where to find those configurations and change them manually if needed.
Run the following command rake db:migrate:down VERSION=<version> where <version> is the version number of your migration file you want to revert. eg. if you want to revert a migration with file name 3846656238_create_users.rb rake db:migrate:down VERSION=3846656238
Put this in your Rakefile above require ‘rake’: require ‘rake/dsl_definition’
rake db:migrate:redo VERSION=xxxxxxx, but that will run the down and then the up step. You could do this in conjunction with commenting out the down step temporarily.
A little bit more explicit, in your \config\deploy.rb, add outside any task or namespace: namespace :rake do desc “Run a task on a remote server.” # run like: cap staging rake:invoke task=a_certain_task task :invoke do run(“cd #{deploy_to}/current; /usr/bin/env rake #{ENV[‘task’]} RAILS_ENV=#{rails_env}”) end end Then, from /rails_root/, you can run: cap staging rake:invoke task=rebuild_table_abc
You can run Rake tasks from your shell by running: rake task_name To run from from Ruby (e.g., in the Rails console or another Rake task): Rake::Task[‘task_name’].invoke To run multiple tasks in the same namespace with a single task, create the following new task in your namespace: task :runall => [:iqmedier, :euroads, :mikkelsen, :orville] do … Read more
Put this in application.rb, or in a rake task initialize code if defined?(Rails) && (Rails.env == ‘development’) Rails.logger = Logger.new(STDOUT) end This is Rails 3 code. Note that this will override logging to development.log. If you want both STDOUT and development.log you’ll need a wrapper function. If you’d like this behaviour only in the Rails … Read more
Running your Rake tasks requires two steps: Loading Rake Loading your Rake tasks You are missing the second step. Normally this is done in the Rakefile, but you have to do it manually here: require ‘rake’ Rails.application.load_tasks # <– MISSING LINE Rake::Task[‘my_task’].invoke
Actually, for some unknown reason, I found the issue was actually because the postgresql role hadn’t been created. Try running: createuser -s -r postgres Note that roles are the way that PostgreSQL maintains database permissions. If there is no role for the postgres user, then it can’t access anything. The createuser command is a thin … Read more
Make sure you’re entering “bundle” update, if you have the bundler gem installed. bundle update If you don’t have bundler installed, do gem install bundler.