63 lines
2.7 KiB
Markdown
63 lines
2.7 KiB
Markdown
Your Ente installation is almost ready!
|
||
|
||
## Required: External Object Storage
|
||
|
||
Before using Ente, configure an S3-compatible object storage provider:
|
||
|
||
1. Open the Cloudron dashboard and select your Ente app.
|
||
2. Launch the file explorer.
|
||
3. Open `/app/data/config/s3.env` and provide values for **all** required keys.
|
||
4. Save the file and restart the app from the Cloudron dashboard.
|
||
5. (Required for cast/slideshow) Configure your S3 bucket’s CORS policy to allow the Ente domains you serve from Cloudron (e.g. `https://ente.due.ren`, `https://accounts.due.ren`, `https://cast.due.ren`, etc.). Without CORS, browsers will block the signed URLs that power the cast slideshow.
|
||
|
||
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)
|
||
|
||
## Required: Secondary Hostnames
|
||
|
||
The installer now asks for dedicated hostnames for the Auth/Accounts/Cast/Albums/Family web apps (via Cloudron `httpPorts`). If you manage DNS outside of Cloudron, create CNAME/A records such as `accounts.<app-domain>`, `auth.<app-domain>`, etc., pointing at the primary app domain. With Cloudron-managed DNS the records are created automatically.
|
||
|
||
## Administration
|
||
|
||
- Use the bundled CLI from the Cloudron web terminal (CLI state lives in `/app/data/cli-data`). On a new deployment initialise it once (this seeds the CLI config, whitelists an admin email, and resets the CLI DB):
|
||
```bash
|
||
# from the Cloudron terminal, logged in as root
|
||
cat <<'EOF' >/cli-data/config.yaml
|
||
endpoint:
|
||
api: https://<your-app-domain>/api
|
||
log:
|
||
http: false
|
||
EOF
|
||
mkdir -p /cli-data/export
|
||
chown cloudron:cloudron /cli-data /cli-data/config.yaml /cli-data/export
|
||
cat <<'EOF' >/app/data/config/museum.override.yaml
|
||
internal:
|
||
super-admins:
|
||
- admin@example.com
|
||
EOF
|
||
rm -f /cli-data/ente-cli.db
|
||
chown cloudron:cloudron /app/data/config/museum.override.yaml
|
||
|
||
cloudron restart --app <your-app-domain>
|
||
|
||
# store your account (enter the OTP emailed to you)
|
||
sudo -u cloudron ente account add
|
||
|
||
# inspect available commands
|
||
sudo -u cloudron ente --help
|
||
```
|
||
Once the account is added you can follow the upstream admin docs for tasks like whitelisting and quota adjustments.
|
||
See the upstream admin guides for further context: [user administration](https://ente.io/help/self-hosting/administration/users) and [CLI reference](https://ente.io/help/self-hosting/administration/cli).
|
||
|
||
- To persist custom Museum settings (for example, seeding super-admin email addresses), create `/app/data/config/museum.override.yaml`. The file is appended to `museum/configurations/local.yaml` on each startup.
|
||
```yaml
|
||
internal:
|
||
super-admins:
|
||
- admin@example.com
|
||
```
|