@@ -87,42 +87,27 @@ Required modifications are: - The password `db_pass` for the local database hold
## Running Engine
There's a convencience script `run.sh` to get engine started
```shell
engine$ ./run.sh
```
The script executes the _default target_, which is usually `dev` for development environments.
You can call this target explicitly too:
```shell
engine$ ./run.sh dev
```
Or run Engine in production mode:
To start the Engine run:
```shell
engine$ ./run.sh prod
engine$ make run
```
For details on the run script, consult the [AURA CLI documentation](https://gitlab.servus.at/aura/meta/-/blob/master/docs/administration/cli.md).
### Starting dependencies
You'll also need to start Engine Core separately.
> Note it should not matter in which order you start Engine and Engine Core.
> Note it should not matter in which order you start Engine and Engine Core. To be on the safe
> site, start Engine Core first.
```shell
engine-core$ ./run.sh
engine-core$ make run
```
Last but not least, Engine API is the target service to store playlogs, health information and details for the [Studio Clock](https://gitlab.servus.at/aura/dashboard-clock).
```shell
engine-api$ ./run.sh
engine-api$ make run
```
In order to have the complete Engine experience, other AURA Components are required to be running too. Checkout the [Meta Repository](https://gitlab.servus.at/aura/meta) on how to run for example AURA Web using Docker Compose.