How kong-chansila/backend-portfolio works
This is a Go backend for a portfolio site: it serves public content and contact submissions, plus a protected CMS and account-management API. The main request path is client → routed middleware/handler → domain service → repository → MySQL. Authentication resolves cookie sessions before protected handlers; adminctl separately bootstraps and manages accounts. The README is empty, so capability coverage follows the routes and source index. Some service-to-repository links rely on indexed references rather than sampled call bodies.
Main entry points: routes.go Route wiring · repositories Domain repositories · admin.go CMS endpoints · auth.go Authentication service
Components 18
API entry
- HTTP server
cmd/api/main.go - Route wiring
internal/routes/routes.go - Request guards
internal/middleware - Configuration
internal/config
Domain workflows
- Auth endpoints
internal/handlers/auth.go - CMS endpoints
internal/handlers/admin.go - Public content
internal/handlers/content.go - Contact intake
internal/handlers/contact.go - Health check
internal/handlers/health.go - Authentication service
internal/services/auth.go - Content service
internal/services/content.go - Translation service
internal/services/translation.go - Contact service
internal/services/contact.go - Audit service
internal/services/audit.go
Persistence
- Domain repositories
internal/repositories - MySQL database
Account operations
- Admin CLI
cmd/adminctl/main.go
Other components
- Site / admin client
Connections 29
- Site / admin client → HTTP server: sends requests
- HTTP server → Route wiring: serves handler
cmd/api/main.go - HTTP server → Configuration: loads settings
cmd/api/main.go - HTTP server → MySQL database: opens connection
cmd/api/main.go - Route wiring → Auth endpoints: routes auth
internal/routes/routes.go - Route wiring → CMS endpoints: routes admin
internal/routes/routes.go - Route wiring → Public content: routes content
internal/routes/routes.go - Route wiring → Contact intake: routes contact
internal/routes/routes.go - Route wiring → Health check: routes health
internal/routes/routes.go - Route wiring → Request guards: wraps handlers
internal/routes/routes.go - Request guards → Authentication service: resolves sessions
internal/middleware/auth.go - Auth endpoints → Authentication service: handles credentials
internal/handlers/auth.go - Auth endpoints → Audit service: records events
internal/handlers/auth.go - CMS endpoints → Content service: manages content
internal/handlers/admin.go - CMS endpoints → Authentication service: manages users
internal/handlers/admin.go - CMS endpoints → Audit service: records admin actions
internal/handlers/admin.go - CMS endpoints → Domain repositories: reads messages
internal/handlers/admin.go - Public content → Content service: fetches site content
internal/handlers/content.go - Contact intake → Contact service: submits message
internal/handlers/contact.go - Content service → Domain repositories: reads and writes content
internal/services/content.go - Content service → Translation service: applies translations
internal/services/content.go - Translation service → Domain repositories: loads translations
internal/services/translation.go - Contact service → Domain repositories: stores submissions
internal/services/contact.go - Authentication service → Domain repositories: uses account stores
internal/services/auth.go - Audit service → Domain repositories: persists audit events
internal/services/audit.go - Domain repositories → MySQL database: queries database
internal/repositories/session.go - Admin CLI → Configuration: loads settings
cmd/adminctl/main.go - Admin CLI → MySQL database: opens connection
cmd/adminctl/main.go - Admin CLI → Authentication service: creates and lists users
cmd/adminctl/main.go