[FEATURE] Set Up the Head Server Infrastructure

PoweredDeveloper commented

2026-07-07 11:17:29 +00:00

Owner

The project currently lacks a centralized environment where the backend, databases, VPN management panel, and supporting services can run and communicate reliably. Without this infrastructure, the MVP components cannot be integrated or tested together.

Describe the solution you'd like

Set up the initial Head Server infrastructure that will serve as the foundation for the MVP deployment.

The implementation should include:

Configure Docker Compose for all Head Server services.
Deploy the FastAPI Backend.
Deploy the Backend PostgreSQL database.
Deploy the 3x-UI Panel.
Deploy the 3x-UI PostgreSQL database.
Deploy an Nginx reverse proxy.
Configure internal Docker networking between services.
Configure environment variable management.
Configure persistent Docker volumes for databases.
Configure database migrations for the Backend.
Configure Nginx routing for Backend APIs and 3x-UI.
Configure centralized logging.
Configure health check endpoints.
Verify communication between:
- Backend ↔ Backend Database
- Backend ↔ 3x-UI Panel (via API)
- 3x-UI ↔ 3x-UI Database

The resulting infrastructure should provide the platform on which all remaining MVP features can be built.

Describe alternatives you've considered

Running all services directly on the host machine.
Using managed cloud services for databases and reverse proxy

Additional context

The initial Head Server is expected to host:

FastAPI Backend
Backend PostgreSQL
3x-UI Panel
3x-UI PostgreSQL
Nginx Reverse Proxy

Additional services such as Redis, monitoring, background workers, and analytics may be introduced in future iterations.

Acceptance Criteria

All services start successfully.
Backend successfully connects to its PostgreSQL database.
3x-UI successfully connects to its PostgreSQL database.
Backend can communicate with the 3x-UI API.
Nginx correctly proxies requests to Backend and 3x-UI.
Database data persists after container restarts.
Health checks report all services as healthy.

Checklist

I have checked that this feature is not already requested.
I am willing to help implement it (optional).

## Is your feature request related to a problem? The project currently lacks a centralized environment where the backend, databases, VPN management panel, and supporting services can run and communicate reliably. Without this infrastructure, the MVP components cannot be integrated or tested together. ## Describe the solution you'd like Set up the initial Head Server infrastructure that will serve as the foundation for the MVP deployment. The implementation should include: - [x] Configure Docker Compose for all Head Server services. - [x] Deploy the FastAPI Backend. - [x] Deploy the Backend PostgreSQL database. - [x] Deploy the 3x-UI Panel. - [x] Deploy the 3x-UI PostgreSQL database. - [x] Deploy an Nginx reverse proxy. - [x] Configure internal Docker networking between services. - [x] Configure environment variable management. - [x] Configure persistent Docker volumes for databases. - [x] Configure database migrations for the Backend. - [x] Configure Nginx routing for Backend APIs and 3x-UI. - [x] Configure centralized logging. - [x] Configure health check endpoints. - [x] Verify communication between: * Backend ↔ Backend Database * Backend ↔ 3x-UI Panel (via API) * 3x-UI ↔ 3x-UI Database The resulting infrastructure should provide the platform on which all remaining MVP features can be built. ## Describe alternatives you've considered * Running all services directly on the host machine. * Using managed cloud services for databases and reverse proxy ## Additional context The initial Head Server is expected to host: * FastAPI Backend * Backend PostgreSQL * 3x-UI Panel * 3x-UI PostgreSQL * Nginx Reverse Proxy Additional services such as Redis, monitoring, background workers, and analytics may be introduced in future iterations. ### Acceptance Criteria * All services start successfully. * Backend successfully connects to its PostgreSQL database. * 3x-UI successfully connects to its PostgreSQL database. * Backend can communicate with the 3x-UI API. * Nginx correctly proxies requests to Backend and 3x-UI. * Database data persists after container restarts. * Health checks report all services as healthy. ## Checklist * [x] I have checked that this feature is not already requested. * [x] I am willing to help implement it (optional).

PoweredDeveloper added this to the Sprint 1 milestone

2026-07-07 11:17:29 +00:00

PoweredDeveloper added the

enhancement

label

2026-07-07 11:17:29 +00:00

PoweredDeveloper self-assigned this

2026-07-07 11:17:29 +00:00