@@ -23,7 +23,7 @@ This page gives insights on extending Aura Engine internals or through the API.
...
@@ -23,7 +23,7 @@ This page gives insights on extending Aura Engine internals or through the API.
AURA Engine as part of the AURA Radio Suite uses an modulear architecture based on a REST API. All external information is retrieved using JSON data-structures.
AURA Engine as part of the AURA Radio Suite uses an modulear architecture based on a REST API. All external information is retrieved using JSON data-structures.
To get the basic architectural overview, visit the [Aura Meta](https://gitlab.servus.at/autoradio/meta) repository.
To get the basic architectural overview, visit [docs.aura.radio](https://docs.aura.radio).
Starting development of engine can be quite tedious, as it requires all most all other AURA components to be up and running.
Starting development of engine can be quite tedious, as it requires all most all other AURA components to be up and running.
...
@@ -36,9 +36,7 @@ For example:
...
@@ -36,9 +36,7 @@ For example:
If you need to test and develop against the Engine's API you'll also need to get the `engine-api` project running.
If you need to test and develop against the Engine's API you'll also need to get the `engine-api` project running.
For a start it is recommended to create a general `aura` project folder. In there you start cloning all the sub-projects. After having all the sub-projects configured, and verified that they are working, take a look at the AURA `meta` project.
For a start it is recommended to create a general `aura` project folder. In there you start cloning all the sub-projects. After having all the sub-projects configured, and verified that they are working, take a look at the `aura/aura` repository.
There's a convenience script to start all of the three main dependencies (Steering, Dashboard, Tank) all at once:
## Engine Components
## Engine Components
...
@@ -80,9 +78,7 @@ Test cases are located in `./tests` are executed by running:
...
@@ -80,9 +78,7 @@ Test cases are located in `./tests` are executed by running:
## API
## API
You can find the AURA API definition here: https://gitlab.servus.at/autoradio/meta/blob/main/development/api-definition.md
You can find the AURA API definition at https://api.aura.radio
OpenAPI definition for Engine API: https://app.swaggerhub.com/apis/AURA-Engine/engine-api/
## Scheduler
## Scheduler
...
@@ -186,4 +182,4 @@ All Engine logs can be found under `./logs`.
...
@@ -186,4 +182,4 @@ All Engine logs can be found under `./logs`.
-[Bare Metal Installation](docs/bare-metal-installation.md)
-[Bare Metal Installation](docs/bare-metal-installation.md)
-[Developer Guide](docs/developer-guide.md)
-[Developer Guide](docs/developer-guide.md)
-[Setting up the Audio Store [meta]](https://docs.aura.radio/en/latest/administration/setup-audio-store.html)
-[Setting up the Audio Store [docs.aura.radio]](https://docs.aura.radio/en/latest/administration/setup-audio-store.html)
