.Env file has to be populated or function performance won't render

[dkinsell]

Description

The user has to enter in their .env variables on the config page and connect the DB before navigating to /dash. If they don't, the function performance page will not render. Currently the default url is the config page and it redirects the user to the function performance page after submitting the variables and connecting the DB, but the user could theoretically bypass that if they went straight to /dash.

Reproduction

• If you already have your .env variables submitted delete the .env file
• If you are spinning up the app for the first time do not submit any of the requested variables on the config page
• Navigate to localhost:3000/dash and the page will not render

System information

System:
OS: macOS 14.5
CPU: (8) arm64 Apple M2
Memory: 130.52 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.15.1 - ~/.nvm/versions/node/v20.15.1/bin/node
npm: 10.7.0 - ~/.nvm/versions/node/v20.15.1/bin/npm
Browsers:
Chrome: 128.0.6613.138
Safari: 17.5

Additional information

We believe this issue can be solved by adding authorization so if the user attempts to navigate to /dash without having the .env file properly configured it will redirect them to the config page.

👨‍👧‍👦 Contributing

• 🙋‍♂️ Yes, I'd love to make a PR to fix this bug!