OpsWorks overrides database.yml / ignores custom JSON

When I deploy the Rails application with OpsWorks, a new database.yml directory is created in the shared directory. It ignores the existing database.yml (which rightfully should not be in the repo), and I also tried to specify custom JSON, but nothing works. Maybe I have the wrong structure?

 { "deploy": { "my-app-name": { "database": { "adapter": "mysql2", "encoding": "unicode", "host": "xxxxxx.rds.amazonaws.com", "port": "3306", "database": "db-name", "pool": "5", "username": "username", "password": "password" } } } } 
+7
source share
2 answers

Using a short name for the application (without a hyphen). I used to use the full name. See: https://forums.aws.amazon.com/message.jspa?messageID=444711

+2
source

See also:

http://wojtek.ziniewi.cz/2013/06/10/custom-symlinks-in-amazon-opsworks-ror-application/

And always remember to check your json stack by going into the console of one of your opsworks servers and typing:

 opsworks-agent-cli get_json 
+4
source

All Articles