v4.3.2

Important

On 4.1.x or older? Read this before upgrading.
4.2.0 was a security release. Some installs won't start, or will behave differently, until a few settings are changed: a real SECRET_KEY, a real database password, and ADMIN_APPROVAL_EMAIL if you send email.

1. Back up your database. Rolling back means restoring that backup.
2. Make the changes in Actions you must take.
3. Follow Upgrading FilaOps. You can go straight to 4.3.2; there's no need to stop at 4.2.0.

Don't use the app's Update Now button, and don't mount the Docker socket to make it work. Upgrade with the commands in the guide.

Warning

Docker: copy your product images onto the volume before upgrading. Before 4.3.2, product images were saved inside the backend container, and upgrading replaces that container. While your current version is still running, from the filaops folder:

docker compose exec backend sh -c 'set -eu; src=/app/static/uploads/products; dst=/app/uploads/products; mkdir -p "$dst"; if [ -d "$src" ]; then cp -a "$src/." "$dst/"; fi; ls "$dst" | wc -l'

It prints how many images are now on the volume (0 is fine if you never uploaded any). If it prints an error instead, don't upgrade until it succeeds.

Fixed

• Product images survive upgrades. Uploaded product images were saved inside the backend container (/app/static/uploads/products) instead of on the uploads volume, so recreating the container (every Docker upgrade) deleted them. They are now saved to /app/uploads/products on the volume. Image links don't change, and images saved before this fix still show for as long as their files exist. In Docker, images uploaded before the last container recreate are already gone and need uploading again.
• License page with an active license. It now says the license is active instead of asking for a key and linking to the license site, drops a "Restart Core" banner that never went away, and shows an unknown activation date as "—" instead of Dec 31, 1969.

Upgrade notes

• Docker: copy product images first (the command above). See Upgrading FilaOps, step 2.
• No database migrations. From 4.3.0 or 4.3.1, copy the images, check out v4.3.2 and rebuild (docker compose up -d --build).
• Coming from 4.1.x or older? Read Upgrading FilaOps first: it starts with the settings 4.2.0 needs, then upgrades straight to 4.3.2.

Full 4.3 notes, including everything new in 4.3.0: https://github.com/BLB3DPrinting/filaops/releases/tag/v4.3.0