Persist Museum configuration for manual edits
This commit is contained in:
@@ -25,3 +25,9 @@ Before you can use Ente, you need to configure an S3-compatible storage service:
|
||||
- The Ente CLI binary is pre-built at `/app/code/ente` inside the app container.
|
||||
- Open the Cloudron web terminal (working directory `/app/code`) and run commands with `./ente ...` or add `/app/code` to your `PATH`.
|
||||
- A writable CLI config template lives at `/app/data/home/.ente/config.yaml` for pointing the CLI to your instance.
|
||||
|
||||
## Museum Server Configuration
|
||||
|
||||
- The active configuration lives at `/app/data/ente/server/configurations/local.yaml` and is created the first time the app starts.
|
||||
- Subsequent restarts leave this file untouched, so you can whitelist admin accounts or adjust other settings as documented by Ente.
|
||||
- Delete the file to regenerate the default template (environment values such as database and S3 credentials are rendered during creation).
|
||||
|
Reference in New Issue
Block a user