Document CLI bootstrap steps
This commit is contained in:
17
README.md
17
README.md
@@ -64,7 +64,22 @@ After installing on Cloudron remember to:
|
||||
super-admins:
|
||||
- admin@example.com
|
||||
```
|
||||
4. Use the bundled Ente CLI for admin tasks via `cloudron exec --app <location> -- sudo -u cloudron ente --help`. The CLI stores its state in `/app/data/cli-data` (exposed inside the container at `/cli-data`) and already trusts your app’s API endpoint. Typical workflow:
|
||||
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):
|
||||
```bash
|
||||
cloudron exec --app ente.cloudron.io -- bash -lc \
|
||||
'cat <<EOF >/cli-data/config.yaml
|
||||
endpoint:
|
||||
api: https://ente.cloudron.io/api
|
||||
log:
|
||||
http: false
|
||||
EOF
|
||||
mkdir -p /cli-data/export
|
||||
chown cloudron:cloudron /cli-data /cli-data/config.yaml /cli-data/export'
|
||||
|
||||
# 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
|
||||
```
|
||||
Afterwards the usual admin commands work as documented. Example:
|
||||
```bash
|
||||
cloudron exec --app ente.cloudron.io -- sudo -u cloudron ente admin list-users --admin-user admin@example.com
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user