document Floppy update process

README.md

@@ -91,19 +91,35 @@ If you later give the app more memory and want Floppy's split worker layout, adj
 
 ## Updating Floppy
 
-This package currently uses:
+This package currently follows Floppy's stable `release` image:
 
 ```dockerfile
 FROM ghcr.io/dannyvfilms/floppy:release
 ```
 
-To refresh to the current stable upstream image, rebuild/update the Cloudron package:
+When a new Floppy version is released:
+
+1. Check the [Floppy releases](https://github.com/dannyvfilms/Floppy/releases) and their release notes.
+2. Increase `version` in `CloudronManifest.json`, for example from `0.1.4` to `0.1.5`. Cloudron requires a new package version for every update.
+3. Log in with the Cloudron CLI and run the update from this repository:
 
 ```bash
+cd floppy-cloudron
+cloudron login my.example.com
 cloudron update
 ```
 
-For fully reproducible production deployments, replace `:release` in the Dockerfile with a specific upstream `:vX.Y.Z` tag after testing that release, then bump the Cloudron package `version`.
+This rebuilds the package and pulls the latest upstream `release` image. The data in `/app/data` and the Cloudron-managed PostgreSQL and Redis services remain in place during the update.
+
+Afterwards, verify the deployment:
+
+```bash
+cloudron logs -f
+```
+
+Confirm that the database migrations completed and that Floppy opens normally before relying on the updated instance.
+
+For reproducible production deployments, replace `:release` in the Dockerfile with a tested upstream `:vX.Y.Z` tag. For each later Floppy update, change that tag and increase the package `version` before running `cloudron update` again.
 
 ## Logs