Files
godoxy/cmd
yusing 6da7227f9b refactor(errs): migrate from gperr.Error to standard Go error interface
This is a large-scale refactoring across the codebase that replaces the custom
`gperr.Error` type with Go's standard `error` interface. The changes include:

- Replacing `gperr.Error` return types with `error` in function signatures
- Using `errors.New()` and `fmt.Errorf()` instead of `gperr.New()` and `gperr.Errorf()`
- Using `%w` format verb for error wrapping instead of `.With()` method
- Replacing `gperr.Subject()` calls with `gperr.PrependSubject()`
- Converting error logging from `gperr.Log*()` functions to zerolog's `.Err().Msg()` pattern
- Update NewLogger to handle multiline error message
- Updating `goutils` submodule to latest commit

This refactoring aligns with Go idioms and removes the dependency on
custom error handling abstractions in favor of standard library patterns.
2026-02-08 12:07:36 +08:00
..

cmd

Main entry point package for GoDoxy, a lightweight reverse proxy with WebUI for Docker containers.

Overview

This package contains the main.go entry point that initializes and starts the GoDoxy server. It coordinates the initialization of all core components including configuration loading, API server, authentication, and monitoring services.

Architecture

graph TD
    A[main] --> B[Init Profiling]
    A --> C[Init Logger]
    A --> D[Parallel Init]
    D --> D1[DNS Providers]
    D --> D2[Icon Cache]
    D --> D3[System Info Poller]
    D --> D4[Middleware Compose Files]
    A --> E[JWT Secret Setup]
    A --> F[Create Directories]
    A --> G[Load Config]
    A --> H[Start Proxy Servers]
    A --> I[Init Auth]
    A --> J[Start API Server]
    A --> K[Debug Server]
    A --> L[Uptime Poller]
    A --> M[Watch Changes]
    A --> N[Wait Exit]

Main Function Flow

The main() function performs the following initialization steps:

  1. Profiling Setup: Initializes pprof endpoints for performance monitoring
  2. Logger Initialization: Configures zerolog with memory logging
  3. Parallel Initialization: Starts DNS providers, icon cache, system info poller, and middleware
  4. JWT Secret: Ensures API JWT secret is set (generates random if not provided)
  5. Directory Preparation: Creates required directories for logs, certificates, etc.
  6. Configuration Loading: Loads YAML configuration and reports any errors
  7. Proxy Servers: Starts HTTP/HTTPS proxy servers based on configuration
  8. Authentication: Initializes authentication system with access control
  9. API Server: Starts the REST API server with all configured routes
  10. Debug Server: Starts the debug page server (development mode)
  11. Monitoring: Starts uptime and system info polling
  12. Change Watcher: Starts watching for Docker container and configuration changes
  13. Graceful Shutdown: Waits for exit signal with configured timeout

Configuration

The main configuration is loaded from config/config.yml. Required directories include:

  • logs/ - Log files
  • config/ - Configuration directory
  • certs/ - SSL certificates
  • proxy/ - Proxy-related files

Environment Variables

  • API_JWT_SECRET - Secret key for JWT authentication (optional, auto-generated if not set)

Dependencies

  • internal/api - REST API handlers
  • internal/auth - Authentication and ACL
  • internal/config - Configuration management
  • internal/dnsproviders - DNS provider integration
  • internal/homepage - WebUI dashboard
  • internal/logging - Logging infrastructure
  • internal/metrics - System metrics collection
  • internal/route - HTTP routing and middleware
  • github.com/yusing/goutils/task - Task lifecycle management