mirror of
https://github.com/dani-garcia/vaultwarden
synced 2024-06-01 19:48:55 +02:00
mention that Docker's --env-file does not unquote values
parent
9e1470898b
commit
414e2914f9
|
@ -7,7 +7,7 @@ A common source of confusion is enabling the admin page (which creates the `conf
|
|||
Note that config settings under the `Read-Only Config` section of the admin page can only be set via environment variables, so you must restart vaultwarden to make changes to them. If you keep these environment variables in a file named `.env`, you can load them as follows:
|
||||
|
||||
* With standalone vaultwarden, by putting `.env` in the current working directory. vaultwarden will attempt to load this file on startup.
|
||||
* With Docker, by using `docker run --env-file <env-file> ...` (to have Docker load the env file) or `docker run -v /path/to/.env:/.env` (to have vaultwarden load the `.env` file from inside the container).
|
||||
* With Docker, by using `docker run --env-file <env-file> ...` (to have Docker load the env file) or `docker run -v /path/to/.env:/.env` (to have vaultwarden load the `.env` file from inside the container). If you use `--env-file`, note that Docker does not unquote values, so make sure to use `key=val` rather than `key="val"` or `key='val'`.
|
||||
* With Docker Compose, by using the [`env_file`](https://docs.docker.com/compose/environment-variables/#the-env_file-configuration-option) directive.
|
||||
|
||||
## Configuration options
|
||||
|
|
Loading…
Reference in a new issue