How srjui/yap works
Yap is a Go web service centered on account registration, login, logout, and password management. The principal flow starts at the Fiber API routes, enters an auth handler, and uses user persistence and/or session state before returning an HTTP result. Startup loads configuration, connects PostgreSQL, migrates the user model, and installs session middleware. A mailer integration exists but is not wired in the shown startup code. Password handlers and middleware are present in the tree, but their internals were not sampled.
Main entry points: main.go Auth routes · session.go Session setup · repository.go User repository · database.go Database connector
Components 18
HTTP API
- Service startup
main.go - Auth routes
main.go
Authentication
- Sign up
internal/auth/signup.go - Log in
internal/auth/login.go - Log out
internal/auth/logout.go - Password operations
internal/auth/password.go - Auth middleware
internal/auth/middleware.go - Input validation
internal/auth/validation.go - Session setup
internal/auth/session.go
Persistence
- User repository
internal/user/repository.go - User model
internal/user/model.go - PostgreSQL
- Database connector
internal/database/database.go - Session store
Runtime support
- Configuration
internal/config/config.go - Email sender
internal/mailer/mailer.go
Other components
- API client
- Resend
Connections 26
- API client → Auth routes: sends requests
main.go - Service startup → Auth routes: registers
main.go - Auth routes → Sign up: routes signup
main.go - Auth routes → Log in: routes login
main.go - Auth routes → Log out: routes logout
main.go - Auth routes → Password operations: routes password
main.go - Auth routes → Auth middleware: protects routes
main.go - Sign up → Input validation: validates input
internal/auth/signup.go - Sign up → User repository: creates user
internal/auth/signup.go - Log in → User repository: looks up user
internal/auth/login.go - Log in → Session setup: uses session
internal/auth/login.go - Log out → Session setup: uses session
internal/auth/logout.go - Password operations → User repository: uses user data
- Service startup → Configuration: loads settings
main.go - Service startup → Database connector: connects database
main.go - Service startup → User model: migrates schema
main.go - Service startup → Session setup: builds sessions
main.go - Database connector → Configuration: uses settings
internal/database/database.go - Database connector → PostgreSQL: opens connection
internal/database/database.go - User repository → Database connector: queries
internal/user/repository.go - User repository → User model: persists
internal/user/repository.go - Session setup → Configuration: uses settings
internal/auth/session.go - Session setup → Session store: configures storage
internal/auth/session.go - Session store → PostgreSQL: stores sessions
- Email sender → Configuration: uses settings
internal/mailer/mailer.go - Email sender → Resend: sends email
internal/mailer/mailer.go