Manually managing database configurations for Rails

If your Rails application uses a MySQL, Postgres or MongoDB instance that is managed by Cloud 66, then we will (by default) automatically amend your database configuration file (specifically database.yml or mongoid.yml). If we don't detect a database configuration file, we will generate one.

We will automatically apply these changes during your deployment.

Custom database configs

If you have significantly customised your database.yml (for example with multiple databases and/or external databases) and you have not disabled our "tampering" (see below) then you may encounter issues.

Disabling automated config updates

If you would prefer to manage these configurations manually you can achieve this using your Manifest file.

This will prevent our system from making any automated changes to the configuration files (including database.yml). You can set this either globally, or per database.

Example of global setting

rails:
	configuration:
		tamper_with_yml: false

Check your configs carefully

Adding this setting means that you need to ensure that the contents of your database configuration(s) are correct as Cloud 66 will no longer be able to update the file(s).

Examples per database

The location of this setting depends on the database type. For example:

MySQL

  mysql:
    configuration:
      tamper_with_yml: false

Postgres

  postgresql:
    configuration:
      tamper_with_yml: false

MongoDB

  mongodb:
    configuration:
      tamper_with_yml: false