This project is a simple dashboard to display usage data collected by the watcher project. You also need to fetch data from a watcher-server. Protected routes can only be acessed by passing the AUTH_TOKEN from the watcher-server.
$ npm installIn the project directory, you can run:
Runs the app in the development mode. Open http://localhost:8000 to view it in the browser.
You can also run in a specific mode using :
$ npm run dev -- --mode development|staging|productionBuilds the app for production to the dist folder. It correctly bundles Solid in production mode and optimizes the build for the best performance. The build is minified and the filenames include the hashes. Your app is ready to be deployed!
Learn more about configuring your environment variables in the documentation. All variables are defined in the example .env file.
This application uses @solidjs/router for client-side routing, providing a seamless user experience. Below is an overview of the available routes and their respective responsibilities:
/auth: This route leads to the authentication page where users can sign in using the AUTH_TOKEN from watcher-server./: Displays the home page of the application, which lists various applications or services available to the authorized user. Unauthorized users are redirected to/auth./:appId/sessions: Shows session information for a specific application. The:appIdparameter in the URL is used to fetch and display session data relevant to the selected application. Also required authentication to be accessed./session/:id/recording: This route is used to display a specific session's recording. The session is identified using the:idparameter in the URL. This is a public route./session/:id/heatmap: Dedicated to showing a heatmap for a particular session. Similar to the session recording route, it uses the:idparameter to specify which session's heatmap to display. Also a public route.
Learn more about deploying your application in the documentation.