Configure optional settings
- 1.To store data externally using Postgres in single-server mode, follow Step 1a in Configure external databases
- 2.To cache session and queueing data externally using Redis in single-server mode, follow Step 1b in Configure external databases
- 3.Private Mode: By default, access to Dash Enterprise is restricted to logged-in users only, including files marked “public” or shared via a “share key”. To make “public” files viewable without authentication, uncheck Enable Private Mode.
- We strongly discourage this if your server is publicly accessible
- If not using LDAP or SAML authentication, disabling Private Mode permits self-serve account creation
- 4.To allow data imports from servers with private or reserved IP addresses such as 10.0.0.1 or 169.254.1.1, enable Allow Data Imports from Private IP Addresses
- If unsure of whether you need this functionality, leave it unchecked
- 5.To retrieve tickets from your KDC to be used by Dash Apps, check Retrieve Kerberos ticket after authentication and specify your default realm and the KDC’s domain name
- 6.To customize the amount of time a user can remain logged in to Dash Deployment Server, specify the time in seconds using in Session length option
- Set to 0 (default) for unlimited session length
- 7.If using Mapbox, check Enable Mapbox Integration and specify your Mapbox Default Access Token and Mapbox Atlas Default Style URL
- Mapbox is not required to access Dash Enterprise’s built-in mapping functionality
- 8.Enable Daily Snapshots to store up to 3 daily snapshots
- 9.Enter a Custom pip index URL to use instead of the public PyPI server
- 10.Specify any Allowed Directories for Mapping desired to allow a non-admin user to map those directories on the host into Dash apps
- All other restrictions still apply
- 11.White-Labeling (Customize Branding):
- You can remove the link from Portal to App Manager by disabling the Display a Link to the App Manager in Portal option
- 1.The link will be removed for both admin and non-admin users
- 2.The App Manager will still remain accessible through URL
- You can remove Plotly branding from all login prompts by selecting the Remove Plotly Logo from Login Window option
- 12.Keep Alive Timeout: Keep Alive timeout defines how long to wait for a new HTTP request to start coming after a response is sent before closing the connection. Some proxies and load balancers like Azure Front Door may require a Keep-Alive timeout higher than the default 1s to serve traffic to Dash Enterprise (90 seconds in the case of Azure Front Door). Otherwise, the 1s default should work.
- 13.Enable Dash Customizations for the following customization options:
- Dash Proxy Configuration
- Dash Web Server Workers
- Dash Web Server Threads per Worker
- Indirect Certificate Mapping
- 1.Removes a direct volume map from the host's
/etc/ssl/certs/ca-certificates.crt
file to the Dash application's/etc/ssl/certs/ca-certificates.crt
file - 2.This allows for locks to be removed that would otherwise cause failures when deploying apps with dependencies that manage their own certificate updates