Skip to content

Commit da68dcb

Browse files
authored
update docs
1 parent e83026e commit da68dcb

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Once it is running, run the following command (from host) to install the extensi
6767
docker compose exec -it my-directus npx directus schema-sync install --force
6868
```
6969

70-
We are using force since we do want to replace the `schema-sync` folder already added as a volumn
70+
We are using force since we do want to replace the `schema-sync` folder already added as a volume
7171

7272
---
7373

@@ -85,6 +85,8 @@ View and edit the schema-sync/*_config.js_ file to include the collections you w
8585
To automatically import and export the schema and data, set the `SCHEMA_SYNC` environment variable to `IMPORT`, `EXPORT` or `BOTH`.
8686
In production it is advised to set `SCHEMA_SYNC` to `IMPORT` and in local development to `BOTH`.
8787

88+
Note: This extension will not work if there is no row in the `directus_settings` database table. To avoid this happening, make sure `PROJECT_NAME` configuration variable is set when Directus is first time installed into the database. Alternatively, if Directus is already installed, just manually create a row in `directus_settings`, if one is not already there, with whatever project name you want and keep everything else to defaults.
89+
8890
### Tips
8991

9092
**Order matters** when importing and exporting. For example if you have a collection (A) with a relation to another collection (B), then ensure in the config that collection (B) comes first. This is so when we import, we first import B, then A. Deletions happen afterward in the reverse order.

0 commit comments

Comments
 (0)