Repository navigation
Important
- A backup job that cannot be saved now says which fields it is waiting on and marks them in the form, instead of only "Could not save the job".
Other
- Error messages from the API reach the UI again. Behind HTTPS they were being discarded on every screen — backups, host monitoring, pings, peers, alerts and settings all showed a generic fallback instead of what the server said.
- The job form checks its required fields before sending, so an incomplete save never makes a round trip.
- Refusals only the server can make — a file that is not a SQLite database, a job name already writing to that folder — now mark the field they name.
- A WAL SQLite database locks the trigger to Cron as soon as the job opens, rather than only after the source file is changed.
- Compose examples read ENCRYPTION_KEY from .env.
- The retention test asserts the kept count rather than a byte-identical folder.
Full changelog: v1.5.0...v1.6.0