rvm-capistrano

How can I instruct Capistrano 3 to load my shell environment variables set at remote host?

夙愿已清 提交于 2019-12-03 16:34:30
问题 I want to instruct Capistrano to load environment variables that are defined on remote server. How can I do that? It seems that when I export my environment variables inside .bashrc file, they are not taken into account by Capistrano. Capistrano seems to be executing a /usr/bin/env to create the environment for executing remote commands, but this does not seem to be loading the environment variables from .bashrc . Let me tell you also that I am using rvm-capistrano too (just in case it might

NoMethodError: undefined method `on' for main:Object

£可爱£侵袭症+ 提交于 2019-12-03 10:26:40
when I try to bundle exec cap production deploy --trace I get an error message: deploy@h2540559:/www/apps/foodsoft$ bundle exec cap production deploy --trace ** Invoke production (first_time) ** Execute production ** Invoke load:defaults (first_time) ** Execute load:defaults ** Invoke rvm:hook (first_time) ** Execute rvm:hook cap aborted! NoMethodError: undefined method `on' for main:Object /usr/local/rvm/gems/ruby-2.0.0-p643/gems/capistrano-rvm-0.1.2/lib/capistrano/tasks/rvm.rake:17:in `block (2 levels) in <top (required)>' /usr/local/rvm/gems/ruby-2.0.0-p643/gems/rake-11.1.1/lib/rake/task.rb

How can I instruct Capistrano 3 to load my shell environment variables set at remote host?

邮差的信 提交于 2019-12-03 06:47:37
I want to instruct Capistrano to load environment variables that are defined on remote server. How can I do that? It seems that when I export my environment variables inside .bashrc file, they are not taken into account by Capistrano. Capistrano seems to be executing a /usr/bin/env to create the environment for executing remote commands, but this does not seem to be loading the environment variables from .bashrc . Let me tell you also that I am using rvm-capistrano too (just in case it might help). Any clue? Delameko Although this question is over six months old now, I'll leave this here in

Missing current folder Capistrano Rails 3.2

旧巷老猫 提交于 2019-12-01 09:30:53
问题 I need to understand why capistrano doesn't create the folder current. I'm using the following command : cap deploy:setup, cap deploy:check, cap deploy But when i check in my app directory, i don't current folder. This my deploy.rb # Execute "bundle install" after deploy, but only when really needed require 'bundler/capistrano' # Automatically precompile assets load "deploy/assets" # RVM integration require "rvm/capistrano" # Application name set :application, "app" # Application environment

Rails console default environment

穿精又带淫゛_ 提交于 2019-11-30 13:47:25
问题 On my development machine: $ bundle exec rails console Loading development environment (Rails 3.2.3) 1.9.3p194 :001 > Rails.env => "development" This is expected. So far, so good. Yet on my production server (to which I have deployed using Capistrano), I get exactly the same result: $ bundle exec rails console Loading development environment (Rails 3.2.3) 1.9.3p194 :001 > Rails.env => "development" On either machine, I can instead do: $ bundle exec rails console production Loading development

Rails console default environment

吃可爱长大的小学妹 提交于 2019-11-30 08:35:18
On my development machine: $ bundle exec rails console Loading development environment (Rails 3.2.3) 1.9.3p194 :001 > Rails.env => "development" This is expected. So far, so good. Yet on my production server (to which I have deployed using Capistrano), I get exactly the same result: $ bundle exec rails console Loading development environment (Rails 3.2.3) 1.9.3p194 :001 > Rails.env => "development" On either machine, I can instead do: $ bundle exec rails console production Loading development environment (Rails 3.2.3) 1.9.3p194 :001 > Rails.env => "production" My question is: on the production

Capistrano error tar: This does not look like a tar archive

拈花ヽ惹草 提交于 2019-11-30 04:08:31
INFO [050fe961] Running mkdir -p /home/rails/rails- capistrano/releases/20140114234157 on staging-rails DEBUG [050fe961] Command: cd /home/rails/rails-capistrano/repo && ( PATH=/opt/ruby/bin:$PATH GIT_ASKPASS=/bin/echo GIT_SSH=/tmp/rails/git-ssh.sh mkdir -p /home/rails/rails-capistrano/releases/20140114234157 ) INFO [050fe961] Finished in 0.142 seconds with exit status 0 (successful). INFO [2dea2fe5] Running git archive feature/Capistrano | tar -x -C /home/rails/rails-capistrano/releases/20140114234157 on staging-rails DEBUG [2dea2fe5] Command: cd /home/rails/rails-capistrano/repo && ( PATH=

Why am I getting a Psych error when trying to deploy with capistrano?

怎甘沉沦 提交于 2019-11-29 11:40:44
I am currently setting up capistrano in my Rails 3.2.13 app. I am getting the below error/details (including "control characters are not allowed at line 1 column 1"). I have done some searching for this but do not see anything related to me. I am using rvm-capistrano and ruby 2.0.0-p195. I recently moved my app-required environment variables into .bashrc. ... * 2013-06-10 15:18:32 executing `deploy:assets:update_asset_mtimes' * executing "[ -e /home/deployer/apps/super_rad_app/shared/assets/manifest* ] && cat /home/deployer/apps/super_rad_app/shared/assets/manifest* || echo" servers: ["107.20

Capistrano error tar: This does not look like a tar archive

好久不见. 提交于 2019-11-29 02:00:15
问题 INFO [050fe961] Running mkdir -p /home/rails/rails- capistrano/releases/20140114234157 on staging-rails DEBUG [050fe961] Command: cd /home/rails/rails-capistrano/repo && ( PATH=/opt/ruby/bin:$PATH GIT_ASKPASS=/bin/echo GIT_SSH=/tmp/rails/git-ssh.sh mkdir -p /home/rails/rails-capistrano/releases/20140114234157 ) INFO [050fe961] Finished in 0.142 seconds with exit status 0 (successful). INFO [2dea2fe5] Running git archive feature/Capistrano | tar -x -C /home/rails/rails-capistrano/releases

Why am I getting a Psych error when trying to deploy with capistrano?

放肆的年华 提交于 2019-11-28 05:50:47
问题 I am currently setting up capistrano in my Rails 3.2.13 app. I am getting the below error/details (including "control characters are not allowed at line 1 column 1"). I have done some searching for this but do not see anything related to me. I am using rvm-capistrano and ruby 2.0.0-p195. I recently moved my app-required environment variables into .bashrc. ... * 2013-06-10 15:18:32 executing `deploy:assets:update_asset_mtimes' * executing "[ -e /home/deployer/apps/super_rad_app/shared/assets