Persist Museum configuration for manual edits

CloudronManifest.json

@@ -7,7 +7,7 @@
   "contactEmail": "contact@ente.io",
   "tagline": "Open Source End-to-End Encrypted Photos & Authentication",
   "upstreamVersion": "1.0.0",
-  "version": "0.1.127",
+  "version": "0.1.128",
   "healthCheckPath": "/ping",
   "httpPort": 3080,
   "memoryLimit": 1073741824,

POSTINSTALL.md

@@ -25,3 +25,9 @@ Before you can use Ente, you need to configure an S3-compatible storage service:
 - The Ente CLI binary is pre-built at `/app/code/ente` inside the app container.
 - Open the Cloudron web terminal (working directory `/app/code`) and run commands with `./ente ...` or add `/app/code` to your `PATH`.
 - A writable CLI config template lives at `/app/data/home/.ente/config.yaml` for pointing the CLI to your instance.
+
+## Museum Server Configuration
+
+- The active configuration lives at `/app/data/ente/server/configurations/local.yaml` and is created the first time the app starts.
+- Subsequent restarts leave this file untouched, so you can whitelist admin accounts or adjust other settings as documented by Ente.
+- Delete the file to regenerate the default template (environment values such as database and S3 credentials are rendered during creation).

start.sh

@@ -207,6 +207,7 @@ MUSEUM_CONFIG_DIR="/app/data/ente/server/configurations"
 MUSEUM_CONFIG="$MUSEUM_CONFIG_DIR/local.yaml"
 mkdir -p "$MUSEUM_CONFIG_DIR"
 
+if [ ! -f "$MUSEUM_CONFIG" ]; then
   log "INFO" "Rendering Museum server configuration"
   cat > "$MUSEUM_CONFIG" << EOF
 # Museum server configuration
@@ -332,6 +333,9 @@ jobs:
 EOF
   chmod 600 "$MUSEUM_CONFIG"
   log "INFO" "Wrote Museum configuration to ${MUSEUM_CONFIG}"
+else
+  log "INFO" "Museum configuration already present at ${MUSEUM_CONFIG}; preserving existing file"
+fi
 
 # ===============================================
 # Database check