When I'm trying to install the plugins by Rake command I'm getting the below error can any one help?
rake redmine:plugins:migrate:RAILS_ENV=production
rake aborted!
Don't know how to build task 'redmine:plugins:migrate:RAILS_ENV'
Note that im using 2.2.0 version
The RAILS_ENV=production part should be prepended to your command.
Try:
RAILS_ENV=production bundle exec rake redmine:plugins:migrate
Related
This is the error I encounter during rake.
The Easy Project cannot start because the Redmine is not migrated!
Please run bundle exec rake db:migrate RAILS_ENV=production and than
bundle exec rake easyproject:install RAILS_ENV=production rake
aborted!
I try to run the command stated and it doesn't work.
Do I need to install something? Because the bundle install is successful.
I thought running the bundle install after giving me the project will do.
The first developer used Linux, but im on Windows.
Already resolved. I used these ffg commands:
bundle exec rake generate_secret_token
set RAILS_ENV=production
bundle exec rake db:migrate
After this error in my web page when i have run > rake db:migrate. It shows error such as:
rake aborted!
you have already activated rake 10.1.1 but you gemfile requires rake 10.1.0 using bundle exec may solve this.
when i tried with bundle exec rake db:migrate it works.
And when i tried with the rake db:migrate. i shows error
My question is:
What is the difference between bundle exec rake db:migrate and rake db:migrate.
every time i have to do like this if yes then why?
What is the problem in my project.
Thanks.
bundle exec rake db:migrate will run rake db:migrate with the environment of your Gemfile.
You have an error because your Gemfile requires a version of rake but you have a newer one installed on your system.
By default, rake will run the latest available version, hence the mismatch.
You should always prefix your commands with bundle exec inside a project managed by bundler, I personally alias bx to bundle exec.
You can also use binstubs
Try to run bundle update.
It seems, that your Gemfile.lock is out of sync with your Gemfile.
My Capistrano deploy:migrate task is set to run a simple rake db:migrate command, as follows:
env PATH=/home/user/.gems/bin sh -c 'cd /home/user/app/releases/20121003140503 && rake RAILS_ENV=production db:migrate'
When I run this task during an ssh session manually it completes successfully. However when I run from my local development box, I receive the following error:
** [out :: app] Could not find rake-0.9.2.2 in any of the sources
I am able to locate my rake gem by typing which rake via ssh (/home/user/.gems/bin/rake) and rake --version gives me "rake, version 0.9.2.2," so I don't understand why this command fails via Capistrano?
Capistrano does not place bundle exec before rake command in default. If you are sure you have the rake gem in your bundle, try adding this to your deploy.rb.
set :rake, 'bundle exec rake'
This will tell Capistrano to instead of just rake run bundle exec rake. If it is in your bundle, you won't have any problems any more and you will also avoid collisions if you have more versions of rake installed on your system.
You might also just need to bundle your gems with this:
require "bundler/capistrano"
Via: Why is Capistrano not installing gems with bundler?
Once you go into your app folder, you simply type:
$bundle exec rake instead of just $rake
I recently installed Rails 3.1 and now my old Rails 3.0 app won't rake db:migrate. This is what happens when I try to run bundle exec rake db:migrate. I'm on Ubuntu with no RVM
/usr/local/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/shared_helpers.rb:142:in `block in cripple_rubygems': can't find executable rake (Gem::Exception)
from /usr/local/lib/ruby/gems/1.9.1/bin/rake:19:in `<main>'
When I run just rake db:migrate, it outputs:
rake aborted!
You have already activated rake 0.9.2.2, but your Gemfile requires rake 0.8.7. Consider using bundle exec.
(See full trace by running task with --trace)
which rake
/usr/local/bin/rake
Put this in your Gemfile:
gem 'rake' , '>= 0.9.2'
and run bundle update
you need to give more details in what environment you're running this:
which OS?
are you using RVM?
is this a brand new RVM setup per chance?
1) Try to run this:
gem list | rake
what output do you get?
2) If you don't see rake in the output, then do this:
gem install rake
and then try rake db:migrate again
3) If you see rake, but it still doesn't work, then do this:
which rake
what output do you get? it should look something like this:
~/.rvm/gems/ruby-1.9.2-p0/bin/rake
heroku rake db:migrate
rake aborted!
no such file to load -- acts_as_ferret
(See full trace by running task with --trace)
(in /disk1/home/slugs/310513_b4b7e61_4c01/mnt)
It show this message issue. how do I fixes this?
add gem in your gem file "acts_as_ferret"
bundle install
run heroku run rake db:migrate
Add the gem act_as_ferret gem.
But seems complicated in heroku environement without ferret.