Hi,
I'm using cap with railsess deploy.
I have a task to update config files that looks like this:
namespace :my do
desc <<-DESC
Create my server config file & copy to release path
DESC
task :update_config_files, :skip_empty_servers => true, :roles => [:my] do
task :update_config_files, :roles => [:my] do
generate_config_files
print " Copying my config files.\n"
upload("files/my/local.inc", "#{release_path}/www/local.inc")
end
end
This is run from a callback:
before 'deploy:symlink', 'my:update_config_files'
I'd like to also be able to update those config files as a separate task
without deploying new code, ie. deploy to the current #{release_path}
without creating a new release.
Now, I could do this by adding a new task that uploads to the symlinked
path something like this:
upload("files/my/local.inc", "/path/to/www/local.inc")
My question is: is there some way to re-use the existing task and deploy
to the latest release, or do I need to create a second task to deploy to
the symlinked path?
Thanks,
R.
--
* 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
