How ORAG Structures Its Go API Startup: Config, Logging, and Error Handling

ORAG, a Go-based API project, manages its server startup through a dedicated run function kept separate from the main entry point in cmd/orag-api/main.go. The startup sequence follows a strict order: configuration is loaded first, followed by logger creation, application initialization, and finally HTTP server startup via the Hertz framework. If any stage fails — such as a missing configuration or a broken app builder — the function logs the error and returns exit code 1 without proceeding further. The application builder and server starter are injected as function dependencies, making the failure paths unit-testable without spinning up a real HTTP server. This design keeps the full initialization lifecycle visible in one place, making it easier to trace and modify individual stages as the project evolves.