Why won’t bundler install JSON gem?
$ bundle update json $ bundle install
$ bundle update json $ bundle install
The error message you’re getting regarding Gemfile.lock may be because your Gemfile and Gemfile.lock don’t agree with each other. It sounds like you’ve changed something in your Gemfile since you last ran bundle install (or update). When you bundle install, it updates your Gemfile.lock with any changes you’ve made to Gemfile. Make sure you run … Read more
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
I had the same issue, until I realized I was pulling the nonexistent branch from git.
You can use the :keep_releases variable to override the default of 5. Check this out.
This works with Capistrano >= 3.1: add this line to config/deploy.rb: set :branch, ENV[‘BRANCH’] if ENV[‘BRANCH’] and then call capistrano with: cap production deploy BRANCH=master This solution works with Capistrano < 3.1: # call with cap -s env=”<env>” branch=”<branchname>” deploy set :branch, fetch(:branch, “master”) set :env, fetch(:env, “production”)
For PHP, SVN with Phing build scripts are the way to go. Phing is similar to ANT but is written in PHP, which makes it much easier for PHP developers to modify for their needs. Our deployment routine is as follows: Everyone develops on the same local server at work, every developer has a checkout … Read more