Properties

New Properties

The following properties are introduced by capistrano-extensions. Many of the Features utilize these properties. Also, check out Code Extensions.

:content_directories —> []

Provides a way to specify which uploadable asset directories (that live in public/) should be retrievable via the local:copy_production_content and local:copy_production tasks described below. Note that this parameter is also utilized by the passenger-recipes gem to keep these uploadable assets in the shared/ context.

:shared_content —> {}

This property is similar to :content_directories, except it doesn’t assume that the symlinks exist in the public/ directory (the default location for FileColumn file storage). This property is a hash of remote => local mappings, e.g. “feeds” => “content” (or “uploaded_assets/meal” => “public/meal”) These examples will effectively create the following symlinks in a deployable environment: ln -sf \#{shared_path}/feeds RAILS_ROOT/content ln -sf \#{shared_path}/uploaded_assets/meal RAILS_ROOT/public/meal Each key (the “remote” directory) must be a directory found in \#{shared_path} (in a deployable environment) Each value (the “local” directory) must be a directory found in RAILS_ROOT (in a local environment)

:deployable_environments —> [:production]

Which environments are deployable— for each environment specified in this array, a helper function by the same name is created that is executed only if RAILS_ENV #is set to that value. See examples/sample_deploy.rb for a code sample.

:config_structure —> :rails

We at SLS use a different config structure than rails does out of the box. Setting this value to :sls will alter some of the expected paths. Normally, you will not have to set this variable. To see a discussion of the SLS config file structure, see http://blog.smartlogicsolutions.com/2008/06/02/better-setup-for-environments-in-rails/ Take a look at environmentalist if you’d like to quickly convert your project’s configuration structure.