Management commands

Django-style commands run with proxium-manage <command>, --help lists them. The examples run from source, in Docker run the same command in the container:

docker exec -it proxium proxium-manage <command>

createsuperuser

Create the first superuser, it prompts for the email and password, SUPERUSER_* variables are ignored. Name and surname are blank unless passed with --name, --surname:

uv run --env-file .env proxium-manage createsuperuser
uv run --env-file .env proxium-manage createsuperuser --email [email protected] --name Ivan

Without prompts, e.g. in scripts, the password comes only from SUPERUSER_PASSWORD, the email from --email or SUPERUSER_EMAIL, name and surname from flags or SUPERUSER_NAME, SUPERUSER_SURNAME, see Configuration:

SUPERUSER_PASSWORD=... uv run --env-file .env proxium-manage createsuperuser --no-input --email [email protected]

With --if-missing a taken email is skipped, not an error, e.g. in start scripts. Other errors still fail:

uv run --env-file .env proxium-manage createsuperuser --no-input --if-missing

changepassword

Set a new password for any user, e.g. a forgotten one, it prompts for it twice:

uv run --env-file .env proxium-manage changepassword [email protected]

migrate

Apply database migrations, up to the latest one or the given revision:

uv run --env-file .env proxium-manage migrate
uv run --env-file .env proxium-manage migrate --wait 60   # wait up to 60s for the database to start

importcert

Add a TLS certificate from PEM files and activate it, see TLS. It asks before turning the active one off, --no-input doesn’t. The same certificate imported again is only activated. The key must have no password:

uv run --env-file .env proxium-manage importcert --cert fullchain.pem --key privkey.pem

rotateencryptionkey

Re-encrypt stored secrets with ENCRYPTION_KEY, reading them with it or ENCRYPTION_OLD_KEYS, see Encryption key:

uv run --env-file .env proxium-manage rotateencryptionkey