Requirements
Kuayle’s documented deployment uses Docker Compose. Review the host, DNS, network and storage requirements before exposing an instance.
Server prerequisites
You need a host that can run Docker Engine and the Docker Compose v2 plugin. A Linux server is the conventional production target. Point a domain at the host if you want Caddy to provision public TLS certificates.
- A host capable of running the current Docker Engine
- Docker Compose v2 plugin
- A domain name pointing to your server (for HTTPS)
Capacity planning
Capacity depends on concurrent users, issue volume, uploads, integrations, and backup retention. Start with enough headroom for PostgreSQL, Redis, image builds, and the application containers, then monitor CPU, memory, and disk use before scaling.
- Allow temporary CPU and disk headroom for container builds and updates
- Monitor PostgreSQL, Redis, and application memory after launch
- Allocate storage for uploads, database growth, and backups
Network requirements
For a public HTTPS deployment, point the domain to the host and allow inbound traffic on ports 80 and 443. Private deployments can use a different TLS and routing design, but must adapt the supplied Caddy configuration.
- Port 80 open — HTTP challenge for Let's Encrypt
- Port 443 open — HTTPS traffic
- Outbound access — image builds, certificate issuance and optional GitHub API calls
Review Kuayle before you deploy it
Inspect the Apache 2.0 source, then follow the Docker Compose guide to run an instance on your infrastructure.