Skip to content

add max users env var and register check #274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 23, 2025
Merged

add max users env var and register check #274

merged 4 commits into from
Jun 23, 2025

Conversation

tavdog
Copy link
Member

@tavdog tavdog commented Jun 22, 2025

fixes #273

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @tavdog, I'm Gemini Code Assist1! 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 introduces a new feature that allows administrators to set a maximum limit on the number of users who can register on the system. This is achieved by introducing a configurable environment variable and integrating a check into the user registration process, ensuring that no new users can sign up once the defined limit is met. This enhances system control and resource management.

Highlights

  • User Management: Implemented a new MAX_USERS configuration option to control the maximum number of registered users allowed on the system.
  • Configuration: The MAX_USERS limit is now configurable via an environment variable. If not explicitly set, it defaults to 100 users.
  • Registration Flow: Added a pre-registration check that prevents new user sign-ups if the MAX_USERS limit has been reached. Users attempting to register beyond the limit will be redirected to the login page with an informative message.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a feature to limit the number of registered users via the MAX_USERS environment variable. There's a critical issue that could cause the application to crash during registration if the environment variable is not set. Additionally, there's a significant performance concern with how the current number of users is calculated, which could impact scalability. I've also included a few suggestions to improve configuration robustness and code consistency.

@@ -25,6 +25,14 @@

@bp.route("/register", methods=("GET", "POST"))
def register() -> ResponseReturnValue:
# Check if max users limit is reached
max_users = int(current_app.config.get("MAX_USERS")) # default to something big
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This line can cause a ValueError if MAX_USERS is set to an empty string in the environment. To make this more robust, you can provide a default value to fall back on if the config value is empty.

max_users = int(current_app.config.get("MAX_USERS") or 100)

# Check if max users limit is reached
max_users = int(current_app.config.get("MAX_USERS")) # default to something big
if max_users > 0:
users_count = len(db.get_all_users())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Calling db.get_all_users() and then len() on the result can be very inefficient, especially if the number of users grows. This function fetches all user data from the database and deserializes it, just to get the count. A more efficient approach would be to get the count directly from the database using a COUNT(*) query.

users_count = db.get_user_count()

@@ -18,3 +18,4 @@ services:
- SYSTEM_APPS_REPO
- PRODUCTION=0
- LOG_LEVEL=DEBUG
- MAX_USERS
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

It's good practice to provide a default value for environment variables in docker-compose.yaml to ensure the service starts correctly even if the variable is not set in the host environment.

MAX_USERS=${MAX_USERS:-100}

@@ -221,6 +221,7 @@ def create_app(test_config: Optional[Dict[str, Any]] = None) -> Flask:
PRODUCTION=os.getenv("PRODUCTION", "1"),
DB_FILE="users/usersdb.sqlite",
LANGUAGES=["en", "de"],
MAX_USERS=os.getenv("MAX_USERS", 100),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To maintain type consistency for the MAX_USERS configuration value, it's better to provide the default value as a string as well. This avoids having a configuration value that is sometimes an integer and sometimes a string.

Suggested change
MAX_USERS=os.getenv("MAX_USERS", 100),
MAX_USERS=os.getenv("MAX_USERS", "100")

@@ -241,6 +242,7 @@
USERS_DIR="tests/users",
DATA_DIR=os.getenv("DATA_DIR", "data"),
PRODUCTION="0",
MAX_USERS=os.getenv("MAX_USERS", 100),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Similar to the production configuration, the default value for MAX_USERS here should be a string to ensure type consistency.

MAX_USERS=os.getenv("MAX_USERS", "100")

@tavdog tavdog merged commit 7bcfb43 into main Jun 23, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a max user count env setting for use on the public instance.
1 participant