How cuongcon3010/field-booking works
Field Booking is a Google OAuth 2.0 sign-in service with a small Next.js interface and a Go/Gin backend. A visitor starts sign-in in the frontend; the backend protects the OAuth callback with state, exchanges the code with Google, creates or links an account, and returns an HttpOnly JWT cookie. The frontend then checks the session and can log out. The README documents account linking, verified-email checks, CORS, and PostgreSQL-backed user and OAuth-account records. Edges reflect shown calls and documented behavior; middleware validation details are not fully sampled.
Main entry points: auth_handler.go Auth endpoints · auth_service.go Account resolution · main.go Gin server · page.tsx Sign-in page
Components 17
Web interface
- Sign-in page
FrontEnd/app/page.tsx
HTTP entry and security
- Gin server
BackEnd/cmd/server/main.go - Auth endpoints
BackEnd/internal/handler/auth_handler.go - CORS policy
BackEnd/internal/middleware/cors_middleware.go - Session middleware
BackEnd/internal/middleware/auth_middleware.go - Runtime config
BackEnd/internal/config/config.go
OAuth and identity
- Google OAuth
- OAuth provider
BackEnd/internal/service/oauth_service.go
Account and session
- Account resolution
BackEnd/internal/service/auth_service.go - JWT service
BackEnd/pkg/jwt/jwt.go
Persistence
- User records
BackEnd/internal/model/user.go - OAuth account records
BackEnd/internal/model/oauth_account.go - User repository
BackEnd/internal/repository/user_repository.go - OAuth repository
BackEnd/internal/repository/oauth_repository.go - PostgreSQL
- Database setup
BackEnd/internal/database/database.go
Other components
- Visitor
Connections 25
- Visitor → Sign-in page: opens
FrontEnd/app/page.tsx - Sign-in page → Auth endpoints: starts login
FrontEnd/app/page.tsx - Sign-in page → Auth endpoints: checks session
FrontEnd/app/page.tsx - Sign-in page → Auth endpoints: requests logout
FrontEnd/app/page.tsx - Gin server → Runtime config: loads
BackEnd/cmd/server/main.go - Gin server → Database setup: initializes
BackEnd/cmd/server/main.go - Gin server → Auth endpoints: registers routes
BackEnd/cmd/server/main.go - Gin server → CORS policy: installs
BackEnd/cmd/server/main.go - Gin server → Session middleware: guards session route
BackEnd/cmd/server/main.go - Auth endpoints → OAuth provider: exchanges code
BackEnd/internal/handler/auth_handler.go - OAuth provider → Google OAuth: requests identity
BackEnd/internal/service/oauth_service.go - Google OAuth → Auth endpoints: returns callback
README.md - Auth endpoints → Account resolution: resolves account
BackEnd/internal/handler/auth_handler.go - Account resolution → User repository: finds or saves user
BackEnd/internal/service/auth_service.go - Account resolution → OAuth repository: finds or links account
BackEnd/internal/service/auth_service.go - Account resolution → JWT service: generates token
BackEnd/internal/service/auth_service.go - Auth endpoints → Sign-in page: redirects after login
BackEnd/internal/handler/auth_handler.go - User repository → PostgreSQL: reads and writes
BackEnd/internal/repository/user_repository.go - OAuth repository → PostgreSQL: reads and writes
BackEnd/internal/repository/oauth_repository.go - Database setup → PostgreSQL: connects and migrates
BackEnd/internal/database/database.go - Database setup → User records: migrates
BackEnd/internal/database/database.go - Database setup → OAuth account records: migrates
BackEnd/internal/database/database.go - Account resolution → User records: creates account data
BackEnd/internal/service/auth_service.go - Account resolution → OAuth account records: creates link data
BackEnd/internal/service/auth_service.go - Session middleware → JWT service: validates token