Skip to main content
The Axottle panel is configured by only through the environment variables with the prefix AXOTTLE_*. There is no separate configuration file in YAML/TOML format: in production, all variables are set in an env file that systemd transmits to the panel process at startup. The configuration is read once at the start of the process, and the full list of default variables is available on ‘s environment variables.
For whom: Administrator, SRE. Required rights: root (or sudo) on the panel server - env file is available only to privileged users.
Any change to any AXOTTLE_* variable will only take effect after the **** axottle service is restarted. editing the env file without restarting does not change the behavior of the running panel.

Where the configuration lives

The main data is stored in the PostgreSQL (DSN is set by the AXOTTLE_DB_URL variable). The migration scheme is applied automatically at each start of the axottle serve - before the panel begins to receive traffic.
The administrator password reset command connects directly to PostgreSQL and must see the configuration of the installed panel.The Doctor also uses this configuration to check the database, but does not stop the diagnosis if PostgreSQL is not available.

Safely modifying the configuration

1

Save the current version of the env file

You’ll need a copy to roll back. Don’t keep backups of the env file in public directories — the file contains secrets.
2

Edit the variables

The format is AXOTTLE_PORT=8080 strings, one variable per row. The real values of the secrets are not shown here - use yours.
3

Restart the service

The restart briefly interrupts access to the panel and API, and when it starts, the panel automatically applies database migrations.
4

Check the health of the panel

Expected response:
Then look at the logs for start errors:

Verification

The panel is considered to be successfully reconfigured when after restart GET /health return "status":"ok", axottle status pointer runningThere are no initialization errors in the logs.
Example of conclusion:
The command ends with non-zero code if the status is different from running – convenient for scripts.

Rollback

1

Return the saved copy.

2

Restart the service and check.

Limitations and risks

  • Restart is mandatory for any change. A modified env file without restart creates a discrepancy between “what’s on the disk” and “what works” – a common cause of diagnosis confusion.
  • Secrets in the env file. AXOTTLE_SECRET_KEY Encrypt the storage of the secrets of the panel, set a strong value in production and restrict access to the file (installer sets). 640 root:axottle - do not weaken these rights. variables.
  • The error DSN base (AXOTTLE_DB_URL) will not allow the panel to rise. Check the logs immediately after restart.

Typical errors

Most likely, the service is not restarted. Run sudo systemctl restart axottle and check systemctl status axottle.
Check the syntax of the file (one variable per line, no spaces around =), then log: journalctl -u axottle -n 100. If the reason is not clear, roll back the file and restart the service.
Run commands on the panel server via sudo. In TUI, open Doctor and select Attempt safe recovery — the tool will try to lift PostgreSQL and repeat the check. If this does not help, check the PostgreSQL container or service and the AXOTTLE_DB_URL configuration in the env file installed panel.

Environment variables

A complete table of all variables of AXOTTLE_*.

CLI axottle

Team status, doctor, logs and others.