For environments where containers are not an option, you can deploy the Hyperterse build artifact directly on a server. The artifact is a self-contained directory — copy it to the target machine, set your environment variables, and start the process.
Deploy the artifact
Build on your CI machine (or locally), then transfer the output:
On the server, start the process:
Process management with systemd
Use a systemd unit to ensure Hyperterse starts on boot and restarts on failure:
Enable and start:
Store credentials in the EnvironmentFile (.env) with restrictive
permissions (chmod 600). Do not embed them in the unit file.
Reverse proxy
Place Hyperterse behind a reverse proxy (nginx, Caddy, HAProxy) for TLS termination, rate limiting, and access control:
Multiple instances
Run multiple Hyperterse processes on different ports behind a load balancer for horizontal scaling:
Each instance is independent with its own in-memory cache. Configure your load balancer to distribute traffic across them.
Checklist
Before going live, verify:
- The process runs as a non-root user.
- Credentials are supplied through environment variables, not hardcoded.
- TLS is terminated at the proxy layer.
- The
/heartbeat endpoint is monitored.
- Log output is routed to your logging infrastructure.
- Automatic restarts are configured (systemd, supervisor, or equivalent).
