Home/ Questions/Q 8555829
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-11T15:12:47+00:00

For some reason Capistrano is failing on just about every operation, because it seems

  • 0

For some reason Capistrano is failing on just about every operation, because it seems to think my current_path should be in /u/apps/. I’ve set all the variables that (AFAIK) should be set, and eliminated all other similar default paths, but this one persists.

Here are the values returned by relevant variables:

current_dir: current
releases_path: /var/www/vhosts/dev.www.example.com/html/releases
shared_path: /var/www/vhosts/dev.www.example.com/html/shared
current_path: /u/apps/www.example.com/current

I’m setting :deploy_to, so shouldn’t current_path be computed based on that!?

set :deploy_to, "/var/www/vhosts/dev.www.example.com/"
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The kind of kludgey solution is just to manually

    set :current_path, ""

    The better solution, which can be found explained in this e-mail thread by Jamis Buck himself, is to use lazy evaluation when you set another variable that depends on current_path. In my case, I had a setting something like this

    set :some_path_var, "#{current_path}/some/path/"

    that I had to change to something like this:

    set(:some_path_var) { "#{current_path}/some/path/" }

    By passing in a block, the :some_path_var was not immediately evaluated, and did not force current_path to be evaluated based on a default value for :deploy_to

    • 0