35 lines
1.7 KiB
Markdown
35 lines
1.7 KiB
Markdown
Your Ente installation is almost ready!
|
|
|
|
## Required: S3 Storage Configuration
|
|
|
|
Before you can use Ente, you need to configure an S3-compatible storage service:
|
|
|
|
1. Go to your Cloudron dashboard
|
|
2. Click on your Ente app
|
|
3. Click on "Terminal"
|
|
4. Edit the S3 configuration file:
|
|
```
|
|
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
|
|
|
|
## 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!
|
|
|
|
## Ente CLI
|
|
|
|
- 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.
|
|
|
|
## 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).
|