Add backup configuration and documentation

- Added backupbot labels to compose.yml:
  - backupbot.backup=true
  - backupbot.backup.path=/data
- Added Backups section to README.md explaining:
  - What paths are backed up (/data)
  - That /music volume is not backed up
  - Manual backup command
- Updated metadata: Backups: Yes

The /data volume contains the SQLite database and configuration files,
which are automatically backed up by backup-bot-two. Music files in
/music are source files and should be backed up separately by users.

README.md

@@ -7,8 +7,8 @@
 * **Category**: Apps
 * **Status**: 2
 * **Image**: [`navidrome`](https://hub.docker.com/r/navidrome), 4, upstream
-* **Healthcheck**: No
-* **Backups**: No
+* **Healthcheck**: Yes
+* **Backups**: Yes
 * **Email**: No
 * **Tests**: No
 * **SSO**: No
@@ -23,3 +23,17 @@
 * `abra app deploy <app-name>`
 
 For more, see [`docs.coopcloud.tech`](https://docs.coopcloud.tech).
+
+## Backups
+
+Backups are handled automatically by [backup-bot-two](https://git.coopcloud.tech/coop-cloud/backup-bot-two).
+
+**Backed up paths:**
+- `/data` - Navidrome database and configuration files
+
+The `/music` volume contains your source music files and is not backed up by backupbot. Ensure you maintain your own backups of your music collection.
+
+To manually trigger a backup:
+```bash
+abra app cmd <app-name> app backup
+```

compose.yml

@@ -28,6 +28,14 @@ services:
         - "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLForceHost=true"
         - "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLHost=${DOMAIN}"
         - "coop-cloud.${STACK_NAME}.version=0.2.0+0.58.0"
+        - "backupbot.backup=true"
+        - "backupbot.backup.path=/data"
+    healthcheck:
+      test: ["CMD", "wget", "-q", "-O", "-", "http://localhost:4533/ping"]
+      interval: 30s
+      timeout: 10s
+      retries: 3
+      start_period: 60s
 
 networks:
   proxy: