docs: add cross-links to initial config and seeding sections

This commit is contained in:
cameronapak
2025-07-16 23:03:38 -05:00
parent cec32ae881
commit 8b832f02ac
2 changed files with 2 additions and 2 deletions

View File

@@ -4,7 +4,7 @@ title: bknd.config.ts
The central configuration file to extend bknd should be placed in the root of your project, so that the [CLI](/usage/cli#using-configuration-file-bknd-config) can automatically pick it up. It allows to: The central configuration file to extend bknd should be placed in the root of your project, so that the [CLI](/usage/cli#using-configuration-file-bknd-config) can automatically pick it up. It allows to:
* define your database connection centrally * define your database connection centrally
* pass in initial configuration or data seeds when booting the first time * pass in [initial configuration](/usage/database#initial-structure) or [data seeds](/usage/database#seeding-the-database) when booting the first time
* add plugins to the app * add plugins to the app
* hook into system events * hook into system events
* define custom routes and endpoints * define custom routes and endpoints

View File

@@ -78,7 +78,7 @@ see [Custom Connection](/usage/database#custom-connection) as a reference.
If the connection object is omitted, the app will try to use an in-memory database. If the connection object is omitted, the app will try to use an in-memory database.
### `initialConfig` ### `initialConfig`
As initial configuration, you can either pass a partial configuration object or a complete one As [initial configuration](/usage/database#initial-structure), you can either pass a partial configuration object or a complete one
with a version number. The version number is used to automatically migrate the configuration up with a version number. The version number is used to automatically migrate the configuration up
to the latest version upon boot. The default configuration looks like this: to the latest version upon boot. The default configuration looks like this: