-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy path.env.example
More file actions
114 lines (102 loc) · 5.01 KB
/
Copy path.env.example
File metadata and controls
114 lines (102 loc) · 5.01 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
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
# This is an example of what your env file should look like.
# You can copy this file and rename it to .env for local use and httpd.env for using our docker configuration.
# Please refer to our documentation on Gitbook: https://pic-sure.gitbook.io/pic-sure-developer-guide/configuring-pic-sure/pic-sure-frontend-configuration
### Application (optional)
VITE_APPLICATION_NAME="PIC-SURE"
VITE_THEME="bdc" # theme from src/styles/theme.css defaults to picsure
VITE_PROJECT_HOSTNAME=picsure.example.com
VITE_ORIGIN=https://picsure.example.com/
### Server Only Resources
RESOURCE_LOG=
LOGGING_API_KEY=
### Auth Providers
# VITE_AUTH_PROVIDER_MODULE is the prefix for any authorization providers you want to use.
# We currently support 3 types of authorization providers: AUTH0, Gen3 FENCE, and RAS.
# You can add as many authorization providers as you want by adding more VITE_AUTH_PROVIDER_MODULE_ variables.
# You can have n number of each type of authorization provider.
# When the server starts it will automatically add the authorization providers to the login page if they are enabled.
# VITE_AUTH_PROVIDER_MODULE_GOOGLE_ALT is an optional field that can be used to specify if the provider should be displayed as an alternative login option.
# The pattern for adding authorization providers is as follows:
# VITE_AUTH_PROVIDER_MODULE_<PROVIDER_NAME>_<FIELD>=<VALUE>
# See https://pic-sure.gitbook.io/pic-sure-developer-guide/configuring-pic-sure/pic-sure-frontend-configuration#login
VITE_AUTH0_TENANT=avillachlab
## Auth0 example
VITE_AUTH_PROVIDER_MODULE_GOOGLE=true
VITE_AUTH_PROVIDER_MODULE_GOOGLE_TYPE=AUTH0
VITE_AUTH_PROVIDER_MODULE_GOOGLE_CLIENTID=12345ABCD
VITE_AUTH_PROVIDER_MODULE_GOOGLE_CONNECTION=oauth2
VITE_AUTH_PROVIDER_MODULE_GOOGLE_DESCRIPTION="Login with Auth0"
VITE_AUTH_PROVIDER_MODULE_GOOGLE_HELPTEXT='Login with your <a href="https://google.com">Google</a> account'
VITE_AUTH_PROVIDER_MODULE_GOOGLE_ALT=false
### Config precedence
# Features/settings/branding are resolved from three layers: the UI's hardcoded defaults,
# the API, and the individual VITE_<KEY> env vars (commented out by default -
# uncomment one to pin/seed that specific field without affecting any other field).
# VITE_CONFIG_MODE decides who wins when both an env var and an API value are set for the
# same field:
# seed (default): defaults -> env (if set) -> API (if set) wins
# override: defaults -> API (if set) -> env (if set) wins
# For string-typed settings, a var counts as "set" if it's present at all, even as an
# empty string - so VITE_GOOGLE_ANALYTICS_ID= (uncommented, blank) is a deliberate
# override to blank, not "unset". Boolean/number/JSON-typed settings can't have a
# meaningful blank value (blank isn't a valid number or JSON, and isn't distinguishable
# from "off"), so for those a blank var falls back to the default just like an absent
# one - use the real value instead (e.g. VITE_DOTS_COLORS_CLASS=[] for a deliberately
# empty list, not VITE_DOTS_COLORS_CLASS=).
VITE_CONFIG_MODE=seed
VITE_API_CONFIG_FEATURES=ui:featureFlag
VITE_API_CONFIG_SETTINGS=ui:setting
VITE_API_CONFIG_BRANDING=ui:branding
### Features
#VITE_OPEN=false
#VITE_DASHBOARD=false
#VITE_DISCOVER=false
#VITE_ANALYZE_API=true
#VITE_ENABLE_TOS=false
#VITE_CONFIRM_EXTERNAL_NAVIGATION=false #Show a confirmation modal before following links to external sites
#VITE_WAF_CAPTCHA_RECOVERY=false #Reload into AWS WAF's CAPTCHA page when WAF intercepts an API call (405 + x-amzn-waf-action header); enable only behind AWS WAF
#VITE_ALLOW_EXPORT=true #Page
#VITE_ALLOW_EXPORT_ENABLED=true #Search Result Icon
#VITE_DASHBOARD_DRAWER=false
#VITE_VARIANT_EXPLORER=true
#VITE_ENABLE_HIERARCHY=true
#VITE_DIST_EXPLORER=true
#VITE_EXPORT_TIMESERIES=false
#VITE_DIST_EXPLORER_GRAPH_COLORS=["#328FFF", "#675AFF", "#FFBC35"]
#VITE_OR_QUERIES=true
#### Export
#VITE_ALLOW_DOWNLOAD=true
#VITE_CONFIRM_DOWNLOAD=true
#VITE_DOWNLOAD_AS_PFB=true
#VITE_MAX_DATA_POINTS_FOR_EXPORT=1000000
#VITE_ENABLE_TERRA_EXPORT=false
#VITE_ENABLE_SAMPLE_ID_CHECKBOX=false
#VITE_SHOW_TREE_STEP=true
#VITE_EXPORT_SYSTEM_FIELDS=
#### Genomic
#VITE_ENABLE_GENE_QUERY=true
#VITE_ENABLE_SNP_QUERY=true
#### Study Auth
#VITE_MANUAL_ROLE=false
#### Tour
#VITE_EXPLORE_TOUR=true
#VITE_EXPLORE_TOUR_SEARCH_TERM=age
#VITE_AUTH_TOUR_NAME=NHANES-Auth
#VITE_OPEN_TOUR_NAME=NHANES-Auth
#Variant Explorer Settings
#VITE_VARIANT_EXPLORER_TYPE=aggregate
#VITE_VARIANT_EXPLORER_MAX_COUNT=10000
#VITE_VARIANT_EXPLORER_EXCLUDE_COLUMNS= # As an array
### UI
# Here you can customize the logo and dot colors on the login page for your project
# To fully change the theme add a new theme to src/styles/theme.css and change the
# data-theme= attribute in the body tag of the main html file, app.html
# You can list 0, 3, or 5 colors in the VITE_DOTS_COLORS_CLASS array
#VITE_LOGO=/app-logo.png #/path/to/logo.svg
#VITE_DOTS_COLORS_CLASS='["--color-primary-500", "--color-error-500", "--color-surface-400"]'
### Analytics (Leave blank to disable)
#VITE_GOOGLE_ANALYTICS_ID=
#VITE_GOOGLE_TAG_MANAGER_ID=
### Additional features
#VITE_ENABLE_TOS=false
#VITE_ENFORCE_TOS_ACCEPT=false