How to Deploy a PR

Pull requests are automatically deployed to a subdomain of wippidu.net by the CI/CD pipeline.

Automatic deployment

When a PR is created or updated:

1. The CI pipeline builds the app and documentation
2. A Docker image is created
3. The app is deployed to pr{N}.wippidu.net where {N} is the PR number
4. Documentation is available at pr{N}.wippidu.net/docs/tech_doc/

The Docker container runs on internal port 50000 + PR number (e.g., PR #3 runs on port 50003).

Branch deployments

Branch	URL	Internal port
PR #{N}	pr{N}.wippidu.net	50000 + N
main	app.wippidu.net	49999
develop	develop.wippidu.net	48888

Cleanup

A daily job automatically:

1. Lists all branches and PRs
2. Checks existing deployments
3. Stops apps for merged/closed PRs
4. Removes stale deployments
5. Updates the deployment list endpoint

Limits

The port-based scheme supports up to 9,999 concurrent PRs (ports 50001–59999). This is well beyond practical needs.