Update POSTINSTALL.md
Fixed Administration setup documentation
This commit is contained in:
@@ -8,7 +8,7 @@ Before using Ente, configure an S3-compatible object storage provider:
|
|||||||
2. Launch the file explorer.
|
2. Launch the file explorer.
|
||||||
3. Open `/app/data/config/s3.env` and provide values for **all** required keys.
|
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.
|
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.
|
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.cloudron.io`, `https://accounts.cloudron.io`, `https://cast.cloudron.io`, etc.). Without CORS, browsers will block the signed URLs that power the cast slideshow.
|
||||||
- **Backblaze B2 tip:** B2 ships with “native” CORS rules that block S3-style updates. Install the Backblaze CLI `pip install 'b2<4'`, then:
|
- **Backblaze B2 tip:** B2 ships with “native” CORS rules that block S3-style updates. Install the Backblaze CLI `pip install 'b2<4'`, then:
|
||||||
```bash
|
```bash
|
||||||
# Authorise once (replace with your key ID/secret)
|
# Authorise once (replace with your key ID/secret)
|
||||||
@@ -61,24 +61,31 @@ The installer now asks for dedicated hostnames for the Auth/Accounts/Cast/Albums
|
|||||||
## Administration
|
## Administration
|
||||||
|
|
||||||
- **Grant yourself admin privileges**
|
- **Grant yourself admin privileges**
|
||||||
1. Open the Cloudron dashboard → your Ente app → **File Manager**.
|
1. Create an Ente account in the UI
|
||||||
2. Navigate to `/app/data/config/` and open (or create) `museum.override.yaml`.
|
2. Open the Cloudron dashboard → your Ente app → **Terminal**.
|
||||||
3. Add your email to the super-admin list:
|
3. Click the Postgres button and hit enter
|
||||||
|
4. Get the user ID of the first user by running the following SQL query: ```SELECT * from users;```
|
||||||
|
5. Copy the value in ```user_id```
|
||||||
|
6. Open the Cloudron dashboard → your Ente app → **File Manager**.
|
||||||
|
7. Navigate to `/app/data/config/` and open (or create) `museum.override.yaml`.
|
||||||
|
8. Add your ```user_id``` to the admin list:
|
||||||
```yaml
|
```yaml
|
||||||
internal:
|
internal:
|
||||||
super-admins:
|
admins:
|
||||||
- you@example.com
|
- 1580559962386438
|
||||||
```
|
```
|
||||||
4. Save the file and restart the app. The override is appended to Museum’s configuration on every start.
|
9. Save the file and restart the app. The override is appended to Museum’s configuration on every start.
|
||||||
|
|
||||||
- **Sign in to the bundled CLI**
|
- **Sign in to the bundled CLI**
|
||||||
*The package now preconfigures the CLI (config: `/app/data/cli-data/config.yaml`, exports: `/app/data/cli-data/export`).*
|
|
||||||
From the Cloudron **Terminal** run:
|
From the Cloudron **Terminal** run:
|
||||||
```bash
|
```bash
|
||||||
# authenticate once (enter the OTP you receive by email)
|
# authenticate once (enter the OTP you receive by email)
|
||||||
sudo -u cloudron ente account add
|
ente account add
|
||||||
|
|
||||||
# inspect available commands
|
# inspect available commands
|
||||||
sudo -u cloudron ente --help
|
ente --help
|
||||||
|
|
||||||
|
# increase storage quota for account
|
||||||
|
ente admin update-subscription -a <admin-user-mail> -u <user-email-to-update> --no-limit true
|
||||||
```
|
```
|
||||||
After you’re signed in you can follow the upstream docs for tasks like increasing storage: see [user administration](https://ente.io/help/self-hosting/administration/users) and the [CLI reference](https://ente.io/help/self-hosting/administration/cli).
|
After you’re signed in you can follow the upstream docs for tasks like increasing storage: see [user administration](https://ente.io/help/self-hosting/administration/users) and the [CLI reference](https://ente.io/help/self-hosting/administration/cli).
|
||||||
|
|||||||
Reference in New Issue
Block a user