everzet/capifony — Issue #77: Issue when using master/slave databases
Author: dlondero
Created: 2011-11-22 12:02:39+00:00
State: open

Hey guys!

I'm setting up Capifony to deploy a large project that runs over more webserver and a master/slave configuration for databases. Webserver's deploy part works well and with

```ruby
set :use_orm, false
```

the task is completed as expected.

Since I'm using sfDoctrineMasterSlavePlugin I (and all people using this plugin for large projects) need a different configuration for databases.yml, below the prod part:

```yml
prod:
master:
class: sfDoctrineDatabase
param:
dsn: 'mysql:host=localhost;dbname=db_name'
username: myusername
password: mypassword
slave:
class: sfDoctrineDatabase
param:
dsn: 'mysql:host=localhost;dbname=db_name'
username: myusername
password: mypassword
```

Because of this configuration when

```ruby
set :use_orm, true
```

deploy process ends up with

```bash
the task `symfony:slave:setup` does not exist
```

mainly because the script doesn't find the "doctrine" key in databases.yml...