AURA Steering is the scheduling module, where the actual program schedule of the
whole station is stored as well as all infos regarding single shows and
AURA Steering is the scheduling module, where the actual program schedule of
the whole station is stored as well as all infos regarding single shows and
emissions.
It also acts as an OpenID Connect provider for `dashboard` and `tank`.
It also acts as an OpenID Connect provider for ``dashboard`` and ``tank``.
Requirements
Installation
------------
- Docker Engine 20.10+
- Docker Compose 2.2+
Follow the instructions to deploy AURA Web from the `Docker Compose
Installation`_.
Quickstart
----------
First build the services::
$ docker compose build
Then, you can setup the database::
$ docker compose run django ./manage.py migrate
You can the load all the fixtures. This loads data for the authentication
(users, groups and permissions) and for the program app (categories, funding
categories, hosts, languages, music focus, recurrence rules, shows, topics and
types).
If you just want to try ``steering`` locally, use the provided compose setup
and be sure to put put ``AURA_PROTO=http`` in the ``.env`` file.
This provides enough data to get started::
A better development setup for ``steering``, that pulls the docker images for
``dashboard`` and ``tank`` from Docker Hub, builds the image for ``steering``
locally and exposes the ports can be achieved with the
``docker-compose.steering.yml`` by adding this lines to the end of the ``.env``
file::
$ docker compose run django ./manage.py loaddata fixtures/*/*.json
Alternatively, if you prefer, you can just create a super user after setting up
the database::
$ docker compose run django python manage.py createsuperuser
The only required fixtures are the recurrence rules, these are needed to create
schedules::
$ docker compose run django ./manage.py loaddata fixtures/program/rrule.json
.. warning:: Currently, if you only create a supert user and load the recurrence rules, you will need to create at least one show using the API in order to use the dashboard.
Then, you can create a RSA Key and the clients for `dashboard` and `tank`::
$ docker compose run django ./manage.py creatersakey
$ docker compose run django ./manage.py create_oidc_client dashboard public -r "id_token token" -u http://localhost:8080/oidc_callback.html -u http://localhost:8080/oidc_callback_silentRenew.html -p http://localhost:8080/
$ docker compose run django ./manage.py create_oidc_client tank confidential -r "code" -u http://localhost:8040/auth/oidc/callback
If you prefer to use the admin interface for this, refer to the [OpenID Client
