bwdata/env/, replace RANDOM_DATABASE_PASSWORD with the password created in Step 3. If using a self-signed certificate, comment out the ssl_trusted_certificate variable. If using a trusted SSL certificate, set the ssl_trusted_certificate variable to the path to your certificate. Take one of the following actions, depending on your certificate setup: Set the ssl_certificate and ssl_certificate_key variables to the paths of the certificate and private key provided in Step 7. Replace all instances of with your domain, including in the Content-Security-Policy header. If you can't provide a trusted SSL certificate, front the installation with a proxy that provides an HTTPS endpoint to Bitwarden client applications. This directory is mapped to the NGINX container at /etc/ssl. GlobalSettings_installation_key=: Enter an installation key retrieved from. GlobalSettings_installation_id=: Enter an installation id retrieved from. GlobalSettings_duo_aKey=: Replace RANDOM_DUO_AKEY with a random key string. GlobalSettings_oidcIdentit圜lientKey=: Replace RANDOM_IDENTITY_KEY with a random key string. GlobalSettings_internalIdentityKey=: Replace RANDOM_IDENTITY_KEY with a random key string. GlobalSettings_identityServer_certificatePassword: Set a secure certificate password for use in a later step. GlobalSettings_sqlServer_ConnectionString=: Replace the RANDOM_DATABASE_PASSWORD with a secure password for use in a later step. GlobalSettings_baseServiceUri_vault=: Enter the domain of your Bitwarden instance. bwdata/env/, edit the following environment variables: You may, if you wish, change the location of these mappings on the host machine. Once unzipped, the bwdata directory will match what the docker-compose.yml file's volume mapping expects.

Docker bitwarden server