⚠️ This page and sub-pages are relevant only if you installed Forest Admin directly on a database (SQL/Mongodb). If you installed in a Rails/Django/Laravel app, you manage your models like you normal
Your models are located in
/models. They control a big part of your Forest UI.
When you install for the first time, Lumber introspects your database and generates your models accordingly.
Afterwards, here's how your database changes can be rendered in your Forest UI:
If you made many changes or even added a new table/collection, we recently reintroduced a programmatic way to help you manage the associated file changes:
This feature requires an agent version 7 or higher.
- Generate files which, after introspecting your database, appear to be missing in your folders (
forest). Eg. Adding a new table and launching
schema:updatewithin your project directory should generate the associated models/routes & forest files
- Generate a correct project architecture to easily manage multiple databases. After your onboarding (on a single database), update the
config/databases.jsfile to add a new connection, launch
schema:updateand your models should be set correctly
forest schema:updatewill never modify your code base (remove files, move files, change file content). It's up to you to copy some (or all) of the generated contents into your existing files/folders.
forest schema:updateoptions are as follows:
--config, allowing to specify a path for the config file to user (Default to
--output-directory: Create a directory named after the config parameter provided. It will also redump all the
models/routes/forestfile in a specific directory, allowing the end-user to pick code modification.
This command need to be launched at the root of the project directory, where the
.envshould be, since it is required by
Lumber does some of the work for you. However, you remain in control of your models.
On the following page, we'll cover how you can enrich your models:
On server start, a
.forestadmin-schema.jsonfile will be auto-generated in local (development) environments only. It reflects:
- the state of your models (in
- your Forest Admin customization (in
This file must be versioned and deployed for any remote environment (staging, production, etc.), as it will be used to generate your Forest UI.
We use the environment variable NODE_ENV to detect if an environment is in development. Setting this variable to either nothing or development will regenerate a new .forestadmin-schema.json file every time your app restarts. Using another value will not regenerate the file.
A consequence of the above is, in Production the
.forestadmin-schema.jsonfile does not update according to your schema changes.
Do not edit this file, as it could break your interface if the wrong syntax is used.
.forestadmin-schema.jsonfile will also help you visualize your changes: