Construido en variables de capistrano

Question

¿Alguien sabe una lista de todas las variables integradas de Capistrano, como current_path y etc.?

Answer 1

Usted puede encontrar todos ellos en:

https://github.com/capistrano/capistrano/blob/legacy-v2/lib/capistrano/recipes/deploy.rb

actualización: ya no V3 tiene las mismas opciones de configuración como v2. Me relacionado las opciones v2 de configuración anterior, pero el V3 tiene las siguientes:

Éstos son los heredados, conservado en este post:

# ========================================================================= 
# These variables MUST be set in the client capfiles. If they are not set, 
# the deploy will fail with an error. 
# ========================================================================= 

_cset(:application) { abort "Please specify the name of your application, set :application, 'foo'" } 
_cset(:repository) { abort "Please specify the repository that houses your application's code, set :repository, 'foo'" } 

# ========================================================================= 
# These variables may be set in the client capfile if their default values 
# are not sufficient. 
# ========================================================================= 

_cset(:scm) { scm_default } 
_cset :deploy_via, :checkout 

_cset(:deploy_to) { "/u/apps/#{application}" } 
_cset(:revision) { source.head } 

_cset :rails_env, "production" 
_cset :rake, "rake" 

# ========================================================================= 
# These variables should NOT be changed unless you are very confident in 
# what you are doing. Make sure you understand all the implications of your 
# changes if you do decide to muck with these! 
# ========================================================================= 

_cset(:source)   { Capistrano::Deploy::SCM.new(scm, self) } 
_cset(:real_revision)  { source.local.query_revision(revision) { |cmd| with_env("LC_ALL", "C") { run_locally(cmd) } } } 

_cset(:strategy)   { Capistrano::Deploy::Strategy.new(deploy_via, self) } 

# If overriding release name, please also select an appropriate setting for :releases below. 
_cset(:release_name)  { set :deploy_timestamped, true; Time.now.utc.strftime("%Y%m%d%H%M%S") } 

_cset :version_dir,  "releases" 
_cset :shared_dir,  "shared" 
_cset :shared_children, %w(public/system log tmp/pids) 
_cset :current_dir,  "current" 

_cset(:releases_path)  { File.join(deploy_to, version_dir) } 
_cset(:shared_path)  { File.join(deploy_to, shared_dir) } 
_cset(:current_path)  { File.join(deploy_to, current_dir) } 
_cset(:release_path)  { File.join(releases_path, release_name) } 

_cset(:releases)   { capture("#{try_sudo} ls -x #{releases_path}", :except => { :no_release => true }).split.sort } 
_cset(:current_release) { releases.length > 0 ? File.join(releases_path, releases.last) : nil } 
_cset(:previous_release) { releases.length > 1 ? File.join(releases_path, releases[-2]) : nil } 

_cset(:current_revision) { capture("#{try_sudo} cat #{current_path}/REVISION",  :except => { :no_release => true }).chomp } 
_cset(:latest_revision) { capture("#{try_sudo} cat #{current_release}/REVISION", :except => { :no_release => true }).chomp } 
_cset(:previous_revision) { capture("#{try_sudo} cat #{previous_release}/REVISION", :except => { :no_release => true }).chomp if previous_release } 

_cset(:run_method)  { fetch(:use_sudo, true) ? :sudo : :run } 

# some tasks, like symlink, need to always point at the latest release, but 
# they can also (occassionally) be called standalone. In the standalone case, 
# the timestamped release_path will be inaccurate, since the directory won't 
# actually exist. This variable lets tasks like symlink work either in the 
# standalone case, or during deployment. 
_cset(:latest_release) { exists?(:deploy_timestamped) ? release_path : current_release } 

_cset :maintenance_basename, "maintenance" 
_cset(:maintenance_template_path) { File.join(File.dirname(__FILE__), "templates", "maintenance.rhtml") } 

Answer 2

Parece que el casquillo 3 ha extendido la se predetermina en múltiples archivos. Aquí está mi reconstrucción basada en la búsqueda de Cap 2 parámetros predeterminados desde el enlace publicado en el Cap 3 rama maestra:

• https://github.com/capistrano/capistrano/blob/ee96c2e77a57c8facf52854eb14d6b57b2b0e5e7/lib/capistrano/defaults.rb
• https://github.com/capistrano/capistrano/blob/aeab6b6a1e5c5e654f35321dcd7438a0659864d0/lib/capistrano/dsl/paths.rb

A partir del segundo enlace se puede observar que algunas variables en V2 se convierte ahora en métodos lector (lo que significa que no es necesario fetch ellos):

• deploy_to
• deploy_path
• CURRENT_PATH
• releases_path
• release_path
• stage_config_path
• deploy_config_path
• repo_url
• repo_path
• shared_path
• revision_log
• ahora
• asset_timestamp