There are settings. There's the set, fetch pair which works nice
set :setting, "value" fetch(:setting,"default value") I'd put that stuff in the deploy.rb and use environment variables to override. A neat way to override would be set :setting,ENV['VAR'] fetch (:setting,"Default value") Unfortunately fetch will return nil as :setting is defined, even though it is nil. Grrr, I'm so hooked on the NullObject pattern that I don't like to see nils anymore. @Lee do you think it would be a good idea to have a fetch!() that returns the default value if key exists or value==nil? Also, because I'm quite new to cap3 as well I might be missing the option switch that allows you to define a setting on the command line. --help though does not give any indication to it's existence. Cheers, V.- -- -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en --- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
