Clarify admin bootstrap steps
This commit is contained in:
@@ -23,7 +23,7 @@ The installer now asks for dedicated hostnames for the Auth/Accounts/Cast/Albums
|
|||||||
|
|
||||||
## Administration
|
## 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:
|
- 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
|
```bash
|
||||||
# from the Cloudron terminal, logged in as root
|
# from the Cloudron terminal, logged in as root
|
||||||
cat <<'EOF' >/cli-data/config.yaml
|
cat <<'EOF' >/cli-data/config.yaml
|
||||||
@@ -34,6 +34,15 @@ log:
|
|||||||
EOF
|
EOF
|
||||||
mkdir -p /cli-data/export
|
mkdir -p /cli-data/export
|
||||||
chown cloudron:cloudron /cli-data /cli-data/config.yaml /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)
|
# store your account (enter the OTP emailed to you)
|
||||||
sudo -u cloudron ente account add
|
sudo -u cloudron ente account add
|
||||||
|
|||||||
13
README.md
13
README.md
@@ -64,7 +64,7 @@ After installing on Cloudron remember to:
|
|||||||
super-admins:
|
super-admins:
|
||||||
- admin@example.com
|
- admin@example.com
|
||||||
```
|
```
|
||||||
4. Use the bundled Ente CLI for admin tasks via `cloudron exec --app <location> -- sudo -u cloudron ente --help`. On a fresh install run the following once (this initialises the CLI’s container-specific config and keystore):
|
4. Use the bundled Ente CLI for admin tasks via `cloudron exec --app <location> -- sudo -u cloudron ente --help`. On a fresh install run the following once (initialises the CLI config, whitelists your admin, and clears the CLI DB):
|
||||||
```bash
|
```bash
|
||||||
cloudron exec --app ente.cloudron.io -- bash -lc \
|
cloudron exec --app ente.cloudron.io -- bash -lc \
|
||||||
'cat <<EOF >/cli-data/config.yaml
|
'cat <<EOF >/cli-data/config.yaml
|
||||||
@@ -74,7 +74,16 @@ log:
|
|||||||
http: false
|
http: false
|
||||||
EOF
|
EOF
|
||||||
mkdir -p /cli-data/export
|
mkdir -p /cli-data/export
|
||||||
chown cloudron:cloudron /cli-data /cli-data/config.yaml /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 ente.cloudron.io
|
||||||
|
|
||||||
# add your account (respond to prompts with the OTP sent to your email)
|
# add your account (respond to prompts with the OTP sent to your email)
|
||||||
cloudron exec --app ente.cloudron.io -- sudo -u cloudron ente account add
|
cloudron exec --app ente.cloudron.io -- sudo -u cloudron ente account add
|
||||||
|
|||||||
Reference in New Issue
Block a user