How nurashi/aiforge works
Project type and purpose
• This is a Go-based, Dockerized microservices system comprising an API Gateway plus two backend services (Auth Service and User Service).
• The API Gateway exposes a unified HTTP interface to clients, forwarding requests to the appropriate microservice.
• The Auth Service handles OAuth login flows, session management (Redis), and user authentication.
• The User Service manages user profiles and project entities.
File structure
• Top-level folders:
• api-gateway – reverse proxy, routing, auth middleware
• auth-service – OAuth callbacks, session store, user repository
• user-service – CRUD handlers for user data and projects
• scripts/init-db.sql – initial database schema
• docker-compose.yml – service definitions and networking
• Common sub-folders in each service: config, database, handlers, middleware, internal/app, repository, models, main.go and Dockerfile.
• Services use Redis (session), likely PostgreSQL or MySQL for persistent storage (see init-db.sql).
• Each service reads config.yml via a config.go loader.