Enable Ente CLI persistence and update docs
This commit is contained in:
@@ -22,33 +22,24 @@ Supported variables:
|
||||
|
||||
## Required: DNS Subdomains
|
||||
|
||||
Ente now serves supporting apps on dedicated hosts. Create DNS records (CNAME or A) for:
|
||||
Ente now serves supporting apps on dedicated hosts. Create DNS records (CNAME or A) and add matching alias domains in Cloudron for:
|
||||
|
||||
- `accounts.<root-domain>`
|
||||
- `auth.<root-domain>`
|
||||
- `cast.<root-domain>`
|
||||
- `albums.<root-domain>`
|
||||
- `family.<root-domain>`
|
||||
- `auth.<app-domain>`
|
||||
- `accounts.<app-domain>`
|
||||
- `cast.<app-domain>`
|
||||
- `albums.<app-domain>`
|
||||
- `family.<app-domain>`
|
||||
|
||||
For example, if you installed the app at `ente.due.ren`, create records for `accounts.due.ren`, `auth.due.ren`, etc., all pointing to `ente.due.ren`. After adding the DNS records, open the Cloudron dashboard → Ente app → Domains tab and add each hostname as an alias. DNS propagation must complete before the `/accounts` and `/auth` apps will accept sessions.
|
||||
For example, if you installed the app at `ente.cloudron.io`, create records for `auth.ente.cloudron.io`, `accounts.ente.cloudron.io`, etc., all pointing to `ente.cloudron.io`, then add each hostname as an alias in the Cloudron dashboard.
|
||||
|
||||
## Next Steps
|
||||
## Administration
|
||||
|
||||
- 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.
|
||||
- Administrative CLI tooling is available inside the container. Open a terminal and run:
|
||||
- Use the bundled CLI from the Cloudron web terminal:
|
||||
```bash
|
||||
cloudron exec --app ente.due.ren -- sudo -u cloudron ente --help
|
||||
cloudron exec --app ente.due.ren -- sudo -u cloudron ente admin --help
|
||||
cloudron exec --app ente.cloudron.io -- sudo -u cloudron ente --help
|
||||
```
|
||||
The CLI stores its state at `/app/data/cli-data` (inside the container it is available at `/cli-data`). Consult the upstream CLI guide for per-command usage, including storage quota adjustments.
|
||||
|
||||
## 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.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.
|
||||
CLI state lives at `/app/data/cli-data` (available inside the container at `/cli-data`).
|
||||
- Follow Ente’s upstream guides to [whitelist administrative accounts](https://ente.io/help/self-hosting/administration/users#whitelist-admins) and to [adjust user storage quotas](https://ente.io/help/self-hosting/administration/cli).
|
||||
|
||||
Logs are streamed to the Cloudron dashboard. For deeper inspection use:
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user