Make some environment variables required for server start

[0xi4o]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @0xi4o, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the application's security posture by enforcing the presence and proper configuration of essential environment variables at server startup. It eliminates insecure default values for critical components like JWT tokens, session secrets, and token hashing, replacing them with strict requirements. This change includes clear guidance for users to generate their own secure secrets, ensuring that the application operates with robust security configurations from the outset and preventing accidental deployment with weak or missing security parameters.

Highlights

• Environment Variable Enforcement: Several critical environment variables related to JWT authentication, session management, and token hashing are now explicitly required for the server to start.
• Enhanced Security: Default fallback values for these sensitive secrets have been removed from the codebase, compelling users to provide unique, securely generated values, thereby reducing potential security vulnerabilities.
• Startup Validation: A new utility function, validateRequiredEnvVarsOrThrow, has been introduced and integrated into the server's initialization process to ensure all mandatory environment variables are correctly set before the application fully launches.
• Improved Configuration Guidance: The .env.example files across the project have been updated with clear comments, indicating which variables are required and providing instructions on how to generate secure values for them.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request strengthens the application's security by enforcing that critical environment variables for authentication and encryption are set at server startup. It removes insecure default values and adds a validation step that provides clear error messages if a required variable is missing. The changes are well-implemented across the configuration files and source code. I've included one suggestion to refactor a small piece of duplicated code for better maintainability.