Closed EtienneDx closed 5 months ago
The backend should be the one to seed the database, using the regular functions used for creating entities. I suggest adding a script that gets triggered at launch if a certain environnement variable is set. The variable could be injected in commands through a flag, or directly set in the CI.
Here's a simplified graph of the goal for this CR.This will need to be further refined during the implementation
Closed with #45
In order to facilitate the checking of new features, a CI can be put into place.
For our purpose, the new CI should, on push:
A separate manual action should start the server when manually triggered:
config.json
to frontend S3 bucket, giving the frontend the URL to the backAnother manual action should stop the server when manually triggered:
A final stack should be used on merge, on close: