-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy path.env.example
More file actions
74 lines (55 loc) · 2.73 KB
/
.env.example
File metadata and controls
74 lines (55 loc) · 2.73 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
# The local test pages
# Only set if not using default protocol ports
# PAGES_HOST_PORT=3443
# PAGES_HOST_INSECURE_PORT=3000
# If hosting the test-pages locally, a value other than "localhost" is needed
PAGES_HOST="https://127.0.0.1"
# (Optional if not running the public tests) Some websites "prequalify" an entered email to
# see if they have an associated account. If they don't, they may disallow password entry or
# force account create workflow, so it is important that this is a real address with
# organizational control, which you've used to create accounts with at the relevant sites.
PUBLIC_TEST_EMAIL="test@example.com" # A real email you control
# The vault that will be used for testing
VAULT_EMAIL="test@example.com" # Your test vault email
VAULT_PASSWORD="testpassword" # Your test vault password
# Bitwarden CLI API environment, used for seeding the vault
CLI_SERVE_HOST="localhost"
CLI_SERVE_PORT=8087
# Targeted vault environment
VAULT_HOST_PORT=8443
VAULT_HOST_INSECURE_PORT=8080
VAULT_HOST_URL="https://localhost"
# (Optional) Specify an an API endpoint returning a vault configuration.
# Used to match a remote server configuration.
REMOTE_VAULT_CONFIG_MATCH="https://api.bitwarden.com/config"
# (Optional) Indicate whether mock ciphers used in live site tests should be included in vault seeding
# INCLUDE_PUBLIC_PAGE_CIPHERS="true"
# (Optional) Specify the root directory filename for the Bitwarden vault JSON import
# you'd like to use (e.g. "vault.json")
# Mock data generation tool: https://www.passwordvaultgenerator.com/
VAULT_IMPORT_FILE=""
# The extension that will have tests running against it
EXTENSION_BUILD_PATH="clients/apps/browser/build"
# Replace bitwarden.example.com with the domain where Bitwarden will be accessed.
BW_DOMAIN="127.0.0.1"
# The database provider you will be using for your Bitwarden server. Available options are sqlserver, postgresql, sqlite, mysql, or mariadb.
BW_DB_PROVIDER="mysql"
# The name of the server on which your database is running.
BW_DB_SERVER="db"
# The name of your Bitwarden database.
BW_DB_DATABASE="bitwarden_vault"
# The username for accessing the Bitwarden database.
BW_DB_USERNAME="bitwarden"
# The password for accessing the Bitwarden database.
BW_DB_PASSWORD="super_strong_password"
# Specify a custom port for database traffic. If unspecified, the default will depend on your chosen database provider.
BW_DB_PORT=3306
BW_ENABLE_SSL="true"
BW_SSL_CERT="ssl.crt"
BW_SSL_KEY="ssl.key"
# (Optional) Enable server Events service
BW_ENABLE_EVENTS="true"
# (Optional) System Administrator Portal access, comma-delimited
adminSettings__admins="test@example.com"
# (Optional) Fill Assist resource manifest URI
globalSettings__baseServiceUri__fillAssistRules="http://localhost:8000/manifest.json"