You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where is the code to host my own copy of the frontend or is that totally deprecated and the new dashboard/frontend is closed source?
DashboardURL: Sets the url where the frontend is running. Unless you are using a custom domain, you should keep this value as https://app.lanthorn.ai/.
DashboardAuthorizationToken: Configures the Authorization header required to sync the processor and the dashboard.
The text was updated successfully, but these errors were encountered:
saket424
changed the title
can i host my own copy of the new react frontend?
can i host my own copy of the new react dashboard/frontend?
May 7, 2021
The backend and frontend hosted in https://app.lanthorn.ai/ are an official version of that prototype and are currently closed source projects. You can use it to easily visualize data and configure a smart-social-distancing processor.
The DashboardURL config is only used if mailing notifications are enabled (so the processor's emails can redirect to lanthorn's web), but the processor is perfectly functional without that (and any other string will result in a broken URL in the email only)
The DashboardAuthorizationToken was recently added, and it is meant to store an auth token, for we are expanding the capabilities of the Lanthorn closed source backend to allow for acting as a wrapper of multiple processors and receiving processed data from them.
#25 (comment)
Where is the code to host my own copy of the frontend or is that totally deprecated and the new dashboard/frontend is closed source?
DashboardURL
: Sets the url where the frontend is running. Unless you are using a custom domain, you should keep this value as https://app.lanthorn.ai/.DashboardAuthorizationToken
: Configures the Authorization header required to sync the processor and the dashboard.The text was updated successfully, but these errors were encountered: