The normal way is to put them (manually, or using your provisioning tool)
into ./shared/config/ - make this a one-time thing, and ensure that some
time after deploy:update_code that they are symlinked to the correct place,
here's a snippet from my deploy.rb:
# Links the development yml file
after "deploy:finalize_update" do
run "ln -s #{shared_path}/config/database.yml
#{latest_release}/config/database.yml"
end
Note, this task is inlined, (it's not a real `named` task) - but it works
perfectly for me… (also, the syntax for ln could be a little shorter, but I
wanted to make clear the behaviour)
- Lee
--
* 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
