Arivu 1.8.3

Arivu 1.8.3 is out. It adds a new way to run Arivu and fixes complete capture on installer hosts.

What’s in it

• Run Arivu with Docker Compose. A two-service stack runs Arivu and complete capture on a container host or a self-hosted platform such as Dokploy. Read Run Arivu with Docker Compose.
• New arivu backup, arivu restore, and arivu healthcheck commands. Containers can now take and restore the same verified backups as the installer.
• Complete capture works again on installer hosts. A folder the capture helper needed was never created, so every complete capture quietly fell back to a plain copy of the page. Your bookmarks were still saved, but without the screenshot and offline HTML. The installer now creates that folder, and complete capture works as intended.
• A stronger capture sandbox in containers. In the Compose stack, the capture browser runs its own sandbox inside an already locked-down container. If the sandbox cannot start, capture stops and Arivu keeps saving pages directly instead of running unprotected. Native installs are unchanged.
• Capture history shows up again. The list of capture attempts for a bookmark came back with empty fields, so you could not see which attempt worked and why the others failed. It now shows each attempt’s status and reason.
• Safer upgrades. The installer now stops before changing anything if a local customisation points at a file the new capture runtime no longer includes, and tells you which one.

Before you upgrade

• Installer hosts: run the upgrade through the one-line bootstrap command, which fetches the new installer first. If you run sudo arivu-installer upgrade from an older installer, run it a second time afterwards so the service changes apply.
• Compose on an AppArmor host such as Ubuntu: install the capture profile before you deploy. The deployment guide has the commands.

Nothing in your data changes. Follow Self-Hosting Arivu for upgrade steps.