/models
. They control a big part of your Forest UI.models
, routes
& forest
). Eg. Adding a new table and launching schema:update
within your project directory should generate the associated models/routes & forest filesconfig/databases.js
file to add a new connection, launch schema:update
and your models should be set correctlyforest schema:update
will 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:update
options are as follows:-c
or --config
, allowing to specify a path for the config file to user (Default to ./config/databases.js
)-o
or --output-directory
: Create a directory named after the config parameter provided. It will also redump all the models/routes/forest
file in a specific directory, allowing the enduser to pick code modification..env
should be, since it is required by config/databases.js
file. .forestadmin-schema.json
file.forestadmin-schema.json
file will be auto-generated in local (development) environments only. It reflects: /models
)./forest
)..forestadmin-schema.json
file does not update according to your schema changes..forestadmin-schema.json
file will also help you visualize your changes: