How to Self-Host FizzyDo Behind OAuth2 Proxy #2253
Unanswered
abdukhashimov
asked this question in
Ideas and Issue Triage
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This setup runs FizzyDo as a private, authenticated application accessible only to users in your Google Workspace or specified email domain.
Architecture
All requests are intercepted by oauth2-proxy for authentication before reaching FizzyDo. No public registration or unauthenticated access is possible.
Prerequisites
Google OAuth Setup
https://your-domain.com/oauth2/callbackEnvironment Configuration
Create a
.envfile in the same directory asdocker-compose.yaml:Generate Required Secrets
Deployment
Clone or create your setup directory:
Create the docker-compose.yaml and .env files (see above)
Start the services:
Check logs:
Access your application:
https://your-domain.comAuthentication Behavior
Restricting Access
Allow only specific domain:
Allow multiple domains:
Allow any Google account:
Maintenance
Docker Compose File
So far above configuration is working for me
Thanks a lot for everyone who contributed to this codebase
Beta Was this translation helpful? Give feedback.
All reactions