dev@example.com hardcoded in database.py

[gcapuzzi]

dev@example.com hardcoded in database.py

[sancheet230]

@gcapuzzi So what should we use then like should we use creds by defining as environment variables or create a separate configuration file or pass them as arguments via command line

[RAWx18]

I researched the auth issue for a week. Current auth works in production but causes problems in development—contributors must add credentials in secret.toml, which isn’t ideal and limits onboarding. Also, local auth means repo owners can’t track contributor activity.

We have 3 options:

1. Prod/dev flag (implemented) but owner can’t track users.
2. Cloud login service needing server setup.
3. Custom token auth (diagram below) using external auth (Google), role selection, token generation, and owner logs all login attempts for visibility.

Summary from diagram:
User logs in via Google → selects role (Admin/Contributor/User) → gets role-based token → Streamlit verifies token → access granted based on role → owner logs all login attempts.

This method improves contributor experience and lets owners track usage.

[RAWx18]

Should i implement this @gcapuzzi ?