Add new databases

​

Add new database

• Stop your agent. The following process will generate files and using nodemon while following this process can cause mis-generation of the .forestadmin-schema.json file.
• Add a new environment variable, inside your .env file (It will be ANOTHER_DB_URL in this example), which represents the connection url string of the database you want to add.
• Edit the database config file located to config/databases.js to add a new object with the following syntax in the array:

[
  {
    name: 'your_first_database_connection',
    // Models associated to a connection should be in a dedicated folder.
    // If your setup already works, you'll need to update the modelsDir associated to your existing connection
    // by changing this variable value
    modelsDir: path.resolve(
      __dirname,
      './models/your_first_database_connection'
    ),
    connection: {
      url: process.env.DATABASE_URL,
      options: {
        /* Database options can be empty, but should match with your requirements */
      },
    },
  },
  {
    name: 'name_of_the_connection',
    modelsDir: path.resolve(__dirname, './models/name_of_the_connection'),
    connection: {
      url: process.env.ANOTHER_DB_URL,
      options: {
        /* Database options can be empty, but should match with your requirements */
      },
    },
  },
];

• Run forest schema:update command and follow instructions.
  • It should generate all the required files. ⚠️ Be aware that existing files will remain untouched when switching from a single database to a multi-database setup. If you made any modifications in the models of your existing connection.
    In this example, you may want to check the freshly generated models that will be located in the ./models/your_first_database_connection folder.
  • As stated on the forest schema:update documentation, when switching from a single to a multiple database setup, existing models in the ./models folder will remain untouched, and you’ll need to move them to the correct location (According to you config/databases.js file) or simply remove them if you never made any modifications on the models themselves.
• Start the agent, and display the added models with the layout editor. Everything should work as expected