Fix Ente Cloudron packaging issues

- Fixed admin-helper.sh to use correct Museum binary path (/app/museum-bin/museum)
- Updated start.sh to handle missing S3 configuration gracefully
  - App now starts in configuration mode when S3 is not configured
  - Shows helpful configuration page instead of failing health checks
  - Properly starts Museum server once S3 is configured
- Updated CloudronManifest.json to version 0.2.2
- All web frontends (photos, accounts, auth, cast, albums, family) verified working
- Museum API server running successfully with S3 storage

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

POSTINSTALL.md

@@ -1,34 +1,38 @@
 Your Ente installation is almost ready!
 
-## Required: S3 Storage Configuration
+## Required: External Object Storage
 
-Before you can use Ente, you need to configure an S3-compatible storage service:
+Before using Ente, configure an S3-compatible object storage provider:
 
-1. Go to your Cloudron dashboard
-2. Click on your Ente app
-3. Click on "Terminal"
-4. Edit the S3 configuration file:
-   ```
+1. Open the Cloudron dashboard and select your Ente app.
+2. Launch the web terminal.
+3. Edit `/app/data/config/s3.env` and provide values for **all** required keys:
+   ```bash
    nano /app/data/config/s3.env
    ```
-5. Uncomment the variables you need and fill in your S3 credentials (AWS S3, Cloudflare R2, MinIO, etc.). The file includes commented examples for the previous Wasabi defaults and a generic Cloudflare R2 setup.
-6. Save the file and restart your Ente app from the Cloudron dashboard
+4. Save the file and restart the app from the Cloudron dashboard.
+
+Supported variables:
+- `S3_ENDPOINT` (e.g. `https://<account>.r2.cloudflarestorage.com`)
+- `S3_REGION`
+- `S3_BUCKET`
+- `S3_ACCESS_KEY`
+- `S3_SECRET_KEY`
+- `S3_PREFIX` (optional path prefix)
 
 ## Next Steps
 
-1. Once S3 is configured, visit your app URL to create an admin account
-2. Configure your mobile apps to use your custom self-hosted server (Settings → Advanced → Custom Server)
-3. Enjoy your private, end-to-end encrypted photo storage! 
+- Visit the app URL and create the first administrator account.
+- Configure the Ente mobile apps to use your custom server (`Settings → Advanced → Custom Server`).
+- Optional: set the environment variables `CLOUDRON_OIDC_IDENTIFIER`, `CLOUDRON_OIDC_CLIENT_ID`, and `CLOUDRON_OIDC_CLIENT_SECRET` to enable Cloudron SSO in the generated Museum config.
 
-## Ente CLI
+## Administration Helpers
 
-- 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 `./ente ...`.
-- The CLI configuration at `/app/data/home/.ente/config.yaml` already points to your instance (`https://<your-domain>/api`).
-- CLI state is stored under `/app/data/cli-data/` so re-logins persist.
+- The Ente CLI binary is shipped at `/app/code/ente`. Run it via the Cloudron web terminal.
+- CLI configuration lives at `/app/data/home/.ente/config.yaml` and already points to `https://<your-domain>/api`.
+- The main Museum configuration is generated at `/app/data/museum/configurations/local.yaml`. Delete this file to regenerate it with updated environment variables.
 
-## 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).
+Logs are streamed to the Cloudron dashboard. For deeper inspection use:
+```bash
+cloudron logs --app <location> -f
+```