-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Disabling or overriding the Vault interface hosting
BlackDex edited this page Oct 4, 2021
·
7 revisions
As a convenience vaultwarden image will also host static files for Vault web interface. You can disable this static file hosting completely by setting the WEB_VAULT_ENABLED variable.
docker run -d --name vaultwarden \
-e WEB_VAULT_ENABLED=false \
-v /vw-data/:/data/ \
-p 80:80 \
vaultwarden/server:latest
Alternatively you can override the Vault files and provide your own static files to host. You can do that by mounting a path with your files over the /web-vault
directory in the container. Just make sure the directory contains at least index.html
file.
docker run -d --name vaultwarden \
-v /path/to/static/files_directory:/web-vault \
-v /vw-data/:/data/ \
-p 80:80 \
vaultwarden/server:latest
Note that you can also change the path where vaultwarden looks for static files by providing the WEB_VAULT_FOLDER
environment variable with the path.
- Which container image to use
- Starting a container
- Using Docker Compose
- Using Podman
- Updating the vaultwarden image
- Overview
- Enabling admin page
- SMTP configuration
- Disable registration of new users
- Disable invitations
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Other configuration
- Using the MariaDB (MySQL) Backend
- Using the PostgreSQL Backend
- Running without WAL enabled
- Migrating from MariaDB (MySQL) to SQLite
- Hardening Guide
- Password hint display
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Fail2Ban Setup
- Fail2Ban + ModSecurity + Traefik + Docker
- Translating the email templates
- Translating admin page
- Customize Vaultwarden CSS
- Disabling or overriding the Vault interface hosting
- Building binary
- Building your own docker image
- Git hooks
- Differences from the upstream API implementation