Public Ops repository
Start from the released Compose file, environment template and deployment documentation.
Self-hosted software
Run AlgoJudge on infrastructure you control
The public AlgoJudge Ops v0.1.0 repository assembles the released Client, Server and Runners into a production-oriented Compose deployment.
Self-hosted software
An installation, not a hosted account
The operator chooses the host, domain, identity provider and execution capacity. AlgoJudge supplies versioned components and operational tooling without taking ownership of the installation's data.
Versioned images
Use published images for the Server, Client, Runner and External-Runner components.
Operational scripts
Prepare, update, back up, restore, roll back and maintain the installation.
Separate Runners
Place evaluation workers on the application host or on machines of their own.
Stand up the stack
AlgoJudge Ops provides the production deployment boundary.
- Clone the public Ops repository
- Configure the documented environment values
- Run preflight checks before starting
- Launch the selected Docker Compose profiles
Operate it over time
The repository includes tools for routine administration rather than only an initial Compose file.
- Back up and restore installation state
- Update images and retain a rollback point
- Enable and leave maintenance mode
- Run documented cleanup and health checks
Choose the topology
Runtime responsibilities remain separable as the installation grows.
- Serve Client and Server behind the provided edge configuration
- Run sandboxing Runners on suitable hosts
- Enable External-Runner only when an external judge is configured
- Connect an OpenID Connect identity deployment