Duplicate creation of admin account when calling 'docker compose run --rm steering initialize'
As described in https://docs.aura.radio/en/latest/administration/aura-web.html#deploy-aura-web deploying AURA requires copying sample.env
to .env
and adding a django admin under AURA_STEERING_SUPERUSER_USERNAME
, respectively set an admin passwordAURA_STEERING_SUPERUSER_PASSWORD
. It's not unlikely that one will choose a username "admin".
However, executing docker compose run --rm steering initialize
will not only read the .env
but also attempt to create a user admin
from reading in the fixtures. Hence, executing the before mentioned sequence will fail when it comes to adding the admin
user from the fixtures as that user has already been added to the database via .env
.
Basically, a workaround is easy: Enter a different user name under AURA_STEERING_SUPERUSER_USERNAME
in .env
and the installation will pass this stage. Nevertheless, you will end up with two different admin users.
Another possibility could be to remove the admin
user from fixtures and leave this step up to reading and creation of the required user from .env
. Or could the username set in AURA_STEERING_SUPERUSER_USERNAME
simply be overridden if the same user has already been createdin the fixtures? (Which leaves the question how the password for the admin
user is set).