ArgueSecure 2.6.1
Prebuilt images: run ArgueSecure from two files, and upgrade with a pull.
Until now, running ArgueSecure meant building the images on your own host.
From this version a release is published as a set of container images, so a
deployment is a docker-compose.yml and a .env, and an upgrade is a pull and
a restart. On Unraid that is the Update button in Compose Manager.
What changed
- Published images for the application and for the assistant runtime, with
ARGUESECURE_VERSIONin.envto pin a version or follow a line. - The compose file pulls by default. Building from source still works.
Upgrading from 2.6.0
- Take a database dump first (see Backups in the README).
- Use the current compose file. It pulls images by default; building from source still works.
- Pin a version if you like with
ARGUESECURE_VERSIONin.env.
Your data directory, keys and database carry over unchanged.
Known limits
- Behind a reverse proxy, the page can come up blank for visitors on public addresses. This is fixed in 2.6.2; upgrade before putting 2.6.1 on the internet.