- 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>
1.5 KiB
1.5 KiB
Your Ente installation is almost ready!
Required: External Object Storage
Before using Ente, configure an S3-compatible object storage provider:
- Open the Cloudron dashboard and select your Ente app.
- Launch the web terminal.
- Edit
/app/data/config/s3.envand provide values for all required keys:nano /app/data/config/s3.env - Save the file and restart the app from the Cloudron dashboard.
Supported variables:
S3_ENDPOINT(e.g.https://<account>.r2.cloudflarestorage.com)S3_REGIONS3_BUCKETS3_ACCESS_KEYS3_SECRET_KEYS3_PREFIX(optional path prefix)
Next Steps
- 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, andCLOUDRON_OIDC_CLIENT_SECRETto enable Cloudron SSO in the generated Museum config.
Administration Helpers
- 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.yamland already points tohttps://<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.
Logs are streamed to the Cloudron dashboard. For deeper inspection use:
cloudron logs --app <location> -f