The mongodb container is responsible of creating a mongodb container with initial metadata.
All files collection created with relative data are in the seed folder and the init script here
To add more collections during the creation of the database:
- add the corresponding file(s) here, keeping the convention:
filename := collectionname.json. - Restart the docker container.
These files are ingested into the database using mongo funcionalities and bypassing the backend, i.e. they are not to be taken as examples to use the backend API.
In the default configuration init.sh, the seeding creates data in the mongodb database used by the backend service (either v4, by default, or v3 if specified otherwise by setting BE_VERSION).
For an explanation of how setting BE_VERSION changes the environment creation see here.
Since v3 and v4 connect to two different DBs, the BE_VERSION environment variable controls which DB should be seeded (dacat for v3 and dacat-next for v4).