Appearance
Update and settings
Update
Ministra has releases of its own. Mintrix checks for them every day and on Check now, and offers the newest one on its update channel (stable or beta) under Settings > Ministra > Update, with its release notes.
Update now, or Schedule for a set time; both ask for your password. An update:
- downloads the new release;
- backs up Ministra's database to
/opt/mintrix/mysql_backups/(*-before-ministra-<version>.ministra.sql.gz); - starts the new version. If it does not start, the previous version and its database are put back.
Boxes lose Ministra's portal while it restarts, usually about a minute, longer when the database changes. Mintrix keeps running, and so do boxes on Mintrix's MAG app. One update runs at a time: Mintrix's, Ministra's or the MAG app's. Updating Mintrix keeps the Ministra you have.
The tab shows which version runs, as Ministra reports it, and the update history.
| The tab says | |
|---|---|
| "needs Mintrix … or newer" | Update Mintrix first (Settings > System Update) |
| "This server's updater cannot update Ministra yet" | Update Mintrix once: it installs the newer updater |
| "the Ministra Mintrix is connected to still reports …" | The update ran on this server, but Mintrix talks to another Ministra, or the container was not replaced. Check the address under Settings > Ministra, and sudo docker compose ps in /opt/mintrix |
| "a local build (dev)" | A Ministra built on the server itself is not updated from the panel |
For a Ministra on another server, see Ministra on its own server.
Settings and data
| Where | What |
|---|---|
/opt/mintrix/.env | Ministra's port, its database passwords and API login (MINISTRA_*). After a change: sudo mintrix-update --version <running version> |
/opt/mintrix/ministra/config/ | Ministra's config.ini and custom.ini. After editing: sudo docker compose restart ministra ministra-cron in /opt/mintrix |
| Docker volumes | Ministra's database, uploaded logos, film posters (ministra_screenshots), themes and installed applications |
custom.ini overrides config.ini. Its database, cache, API and Mintrix settings are rewritten from .env on every start, so change those in .env.
When saving to Ministra fails
Mintrix saves to Ministra first: a device, subscriber, channel or film is saved only once Ministra has it. When that fails, the message says why: Ministra cannot be reached, it refused Mintrix's login, it answered with an error, or Mintrix has no valid licence. The System Log has the details. See Troubleshooting.