yusing/godoxy: High-performance reverse proxy and container orchestrator for self-hosters

!GitHub last commit

!Demo

A lightweight, simple, and performant reverse proxy with WebUI.

Website | Wiki | Discord

EN | 简体中文 | 繁體中文

Have questions? Ask ChatGPT! (Thanks to @ismesid)

Running demo

Quick start

Configure Wildcard DNS Record(s) to point to machine running GoDoxy, e.g.

• A Record: *.domain.com -> 10.0.10.1
• AAAA Record (if you use IPv6): *.domain.com -> ::ffff:a00:a01

[!NOTE]

GoDoxy is designed to be running in host network mode, do not change it.

> To change listening ports, modify .env.

1. Prepare a new directory for Docker Compose and config files.

1. Run setup script inside the directory, or set up manually

/bin/sh -c "$(curl -fsSL https://raw.githubusercontent.com/yusing/godoxy/main/scripts/setup.sh)"

1. Start the docker compose service from generated compose.yml:

docker compose up -d

1. You may now do some extra configuration on WebUI https://godoxy.yourdomain.com

Key features

• Simple setup

• Automatic routing

• Traffic management

• Access control

• Idle sleep

• Proxmox integration

• Platform support

How GoDoxy works

1. List all the containers
2. Read container name, labels, and port configurations for each of them
3. Create a route if applicable (a route is like a "Virtual Host" in NPM)
4. Watch for container / config changes and update automatically

[!NOTE]

GoDoxy uses the label proxy.aliases as the subdomain(s), if unset it defaults to the container_name field in docker compose.

> For example, with the label proxy.aliases: qbt you can access your app via qbt.domain.com.

Screenshots

idlesleeper

!idlesleeper

Metrics and Logs

Routes	Servers

Proxmox Integration

GoDoxy can automatically discover and manage Proxmox nodes and LXC containers through configured providers.

Automatic Route Binding

Routes are automatically linked to Proxmox resources through reverse lookup:

1. Node-level routes (VMID = 0): When hostname, IP, or alias matches a Proxmox node name or IP
2. Container-level routes (VMID > 0): When hostname, IP, or alias matches an LXC container

routes:
  pve-node-01:
    host: pve-node-01.internal
    port: 8006
    # Automatically links to Proxmox node pve-node-01

WebUI Management

From the WebUI, you can:

• LXC Lifecycle Control: Start, stop, restart containers
• Node Logs: Stream real-time journalctl or log files output from nodes
• LXC Logs: Stream real-time journalctl or log files output from containers

Update / uninstall system agent

Installer supports both systemd and Alpine/OpenRC (rc-service) hosts.

Update:

sh -c "$(curl -fsSL https://github.com/yusing/godoxy/raw/refs/heads/main/scripts/install-agent.sh)" -- update

Uninstall:

sh -c "$(curl -fsSL https://github.com/yusing/godoxy/raw/refs/heads/main/scripts/install-agent.sh)" -- uninstall

Manual Setup

1. Make config directory then grab config.example.yml into config/config.yml

1. Grab .env.example into .env

1. Grab compose.example.yml into compose.yml

Folder structure

├── certs
│   ├── cert.crt
│   └── priv.key
├── compose.yml
├── config
│   ├── config.yml
│   ├── middlewares
│   │   ├── middleware1.yml
│   │   ├── middleware2.yml
│   ├── provider1.yml
│   └── provider2.yml
├── data
│   ├── metrics # metrics data
│   │   ├── uptime.json
│   │   └── system_info.json
└── .env

Build from source

1. Clone the repository git clone https://github.com/yusing/godoxy --depth=1

1. Install / Upgrade go (>=1.22) and shadowtree if not already

1. Clear cache if you have built this before (go < 1.22) with go clean -cache

1. Get dependencies with shadowtree mod-tidy

1. Build binary with shadowtree build

Star History