Details about semver of the recipe

Spell out how we update the release versions of the recipe, specifically
wrt dependencies.

.env.sample

@@ -6,8 +6,6 @@ ENABLE_BACKUPS=true
 DOMAIN=nextcloud.example.com
 ## Domain aliases
 #EXTRA_DOMAINS=', `www.nextcloud.example.com`'
-# space separated list of trusted domains, only evaluated on first startup
-#EXTRA_DOMAINS_TRUSTED=cloud.coquest.coop
 LETS_ENCRYPT_ENV=production
 
 COMPOSE_FILE="compose.yml"

MAINTENANCE.md

@@ -38,7 +38,7 @@ In order to meet these responsibilities each maintainer:
 ## Release cadence
 
 The intent is to **track Nextcloud's own release schedule** rather than invent
-our own. In practice this means:
+our own. In practice this means the following regarding new **nextcloud** releases:
 
 - **Patch releases (e.g. `32.0.x`)**: published to this recipe shortly after
   upstream, ideally within 1 week. `chore(deps)` opens the PRs; a maintainer
@@ -63,6 +63,23 @@ our own. In practice this means:
 - **Co-installed components** (Talk HPB, OnlyOffice, Whiteboard, etc.) are
   bumped alongside or shortly after the matching Nextcloud release.
 
+## Semver versioning within this recipe
+
+The recipe version itself is updated according to the following semver
+rules, following
+[How are recipes versioned](https://docs.coopcloud.tech/maintainers/handbook/#how-are-recipes-versioned):
+
+- **Patch releases**, e.g., 14.1.x: patch updates from the dependencies
+  or patch updates from the nextcloud image
+- **Minor releases**, e.g. 14.x.0: minor updates from the dependencies,
+  major updates from the dependencies if no user intervention is needed,
+  minor updates from the nextcloud image, or "auto-update" version, e.g.,
+  nextcloud:32. 
+  Contrary to patch releases, minor releases cannot be reverted, so you
+  cannot go from 14.1.0 back to 14.0.1.
+- **Major releases**, e.g., 14: dependency updates where the user has to
+  intervene, or major updates from the nextcloud image.
+
 ## Pull Requests
 
 A pull request can be merged once it is approved by at least one maintainer.

README.md

@@ -24,20 +24,6 @@ Fully automated luxury Nextcloud via docker-swarm.
 * `abra app secret generate -a <app-name>`
 * `abra app deploy <app-name>`
 
-### Accessing nextcloud from multiple domains
-
-If you want to access the nextcloud instance from multiple domains, add the additional domains by using both env vars:
-
-```
-EXTRA_DOMAINS=', `nextcloud.example2.com`' # comma separated, for traefik
-EXTRA_DOMAINS_TRUSTED=nextcloud.example2.com # space separated, for nextcloud
-```
-`EXTRA_DOMAINS_TRUSTED` is only evaluated by nextcloud on the first install. If you want to add domains later, you need to run this command additionally:
-```
-abra app cmd nextcloud.example.com app run_occ '"config:system:set trusted_domains <index> --value="nextcloud.example2.com""'
-```
-The indices 0 and 1 are taken, start with 2 for the first extra domain.
-
 ### Onlyoffice Integration
 
 First, install onlyoffice following the instructions in the 

compose.yml

@@ -70,7 +70,7 @@ services:
       - STACK_NAME
       - NEXTCLOUD_ADMIN_USER=${ADMIN_USER}
       - NEXTCLOUD_ADMIN_PASSWORD_FILE=/run/secrets/admin_password
-      - NEXTCLOUD_TRUSTED_DOMAINS=${DOMAIN} ${EXTRA_DOMAINS_TRUSTED}
+      - NEXTCLOUD_TRUSTED_DOMAINS=${DOMAIN}
       - TRUSTED_PROXIES=10.0.0.0/8
       - REDIS_HOST=cache
       - OVERWRITEPROTOCOL=https