Proxy Stack

Reference Docker Compose deployment for Proxy Platform v2.

Overview

Proxy Stack provides reproducible local and production-oriented compositions for PostgreSQL, LavinMQ, IP Judge, Proxy Checker, and Proxy Scheduler. Status: foundation planning. Compose files and pinned image versions will be added through roadmap issues.

Architecture

PostgreSQL <-> Proxy Scheduler <-> LavinMQ
                      |
                      v
                Proxy Checker -> IP Judge

Prometheus / Grafana / Loki observe the stack

The shared message and API shapes are owned by proxy-contracts.

Features

Planned capabilities:

• Local Docker Compose profile
• Production-oriented Compose profile
• Database migration lifecycle
• Health checks and dependency readiness
• Prometheus, Grafana, and Loki integration
• Documented image and configuration overrides

Installation

No runnable release is available yet. Clone the repository to review the specifications and follow the v0.1 issues for the initial implementation.

git clone https://github.com/ichinya/proxy-stack.git
cd proxy-stack

Docker

Docker Compose is the primary deliverable. The local and production profiles will be documented when their roadmap issues are implemented.

Configuration

Non-secret defaults may live in an example environment file. Passwords and deployment credentials must be supplied outside Git and production examples must not contain usable credentials.

Environment variables

Variable	Purpose
POSTGRES_DB	Reference database name
POSTGRES_USER	Reference database user
POSTGRES_PASSWORD	Database secret; never commit a real value
AMQP_USER	Broker user
AMQP_PASSWORD	Broker secret; never commit a real value
STACK_VERSION	Pinned component image version

Names and defaults are proposed and may change before v0.1. Never commit production secrets.

Development

The primary development surface is Docker Compose.

1. Choose an open roadmap issue and confirm its acceptance criteria.
2. Keep contracts and examples versioned; coordinate cross-repository changes explicitly.
3. Add tests for behavior changes and update documentation in the same pull request.
4. Run the repository-specific checks documented by the implementation once they exist.

See CONTRIBUTING.md for the common workflow and SECURITY.md for private vulnerability reporting.

Roadmap

• v0.1 Foundation: repository structure, documentation, Docker/CI foundations, and base contracts.
• v0.2 MVP: collector -> scheduler -> MQ -> checker -> judge -> database -> site working cycle.
• v1.0 Production: multi-region judges, scoring, API, billing, monitoring, and high availability.

Track delivery in the repository milestones and issues.

Related projects

• ip-judge
• proxy-checker
• proxy-collector
• proxy-scheduler
• proxy-contracts
• proxy-site
• proxy-infrastructure

License

MIT License