- a pre-generated engine dataset is being used once the front-end setup is being started
- the front-end setup can still be started with triggering the new data-generation
Right now when starting the front-end setup with yarn run start-backend the engine+elasticsearch is started and the back-end build+ setup. In addition, we're genrating data in the engine. The last step introduces some problems:
- the data generation takes about 10-15 min
- during that time a lot of CPU resources are being used
Since it's always the same dataset we're generating, we could just use a pre-generated data set.