Capistrano does not know anything about database.yml. When it needs to connect to a server, it uses whatever you have configured in your deploy.rb.
The data in database.yml is ONLY used when connecting to the actual database, not when logging into the machine which is running the database. If you do not have login access to the database machine, then you should set one of your other servers to be in the :db role. A server can be in multiple roles. The :db role is only used for determine the server from which migrations will be run. - Jamis On 8/2/07, redbaritone <[EMAIL PROTECTED]> wrote: > > I'm using a Capistrano 2 to cold deploy a rails app (using > railsmachine/recipes in order to take advantage of the mongrel tasks). > I've created an after_update_code task to copy my production > database.yml to the config folder. All of this works well. However, > when it gets to the migration task, it tries to use my server account > (:user in deploy.rb) instead of the user given in the (production) > database.yml file. Any ideas what may be going wrong? > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
