use something like this in your recipe:
set :config_dir, "#{deploy_to}/config"
task :after_setup do
run "mkdir #{config_dir}"
end
task :after_update_code do
run "cp #{config_dir}/* #{release_path}/config"
end
put your server config files (database.yml, s3 config file etc...) in your
server config_dir and you will be fine.
code not tested, use at your own risk ;)
Matt
--
m|a consulting
--------
(760) 536-4425
Skype: mattdesktop
GTalk: [EMAIL PROTECTED]
blog: http://railsontherun.com
On 8/7/07, Jordan A. Fowler <[EMAIL PROTECTED]> wrote:
>
> Trying to figure out the best/cleanest way to keep a database.yml file out
> of version control but available to my production code when doing a
> Capistrano deploy. Currently, I have an svn:ignore on config/database.yml so
> that anyone working on the project can have their own. But of course when I
> deploy, there is no database.yml... Help?
>
> --------------------------------------------------------------
> Jordan A. Fowler
> 1830 Market St. #4
> San Diego, CA 92102
> E-mail: [EMAIL PROTECTED]
> AIM: virtuosojordan
> Phone: 406.546.8055
>
>
>
> _______________________________________________
> Sdruby mailing list
> [email protected]
> http://lists.sdruby.com/mailman/listinfo/sdruby
>
>
_______________________________________________
Sdruby mailing list
[email protected]
http://lists.sdruby.com/mailman/listinfo/sdruby
