RightSide Docs
Deployment

A small workload contract.

RightSide’s founder wedge is intentionally narrow: a database-free HTTP application that can be built, health-checked, activated, logged, and rolled back.

Prepare the application

  • Listen on 0.0.0.0, not only localhost.
  • Read the port from the injected PORT environment variable.
  • Return a successful response from the configured health path. The default is /; configure /health explicitly if the app provides it.
  • Keep secrets out of the image and repository.
  • Use a deterministic build with a non-root runtime where practical.

Optional project configuration

{
  "name": "my-app",
  "healthPath": "/health",
  "public": ["/*"]
}

Save this as poligonhost.json. The compatibility filename remains in use during the staged product rename.

Deploy

rightside deploy . --name my-app

On redeploy, the saved project name can remove the need for the flag. RightSide builds an immutable candidate, starts it in an isolated runtime, checks health, activates the route, and returns structured stage results.

Inspect and operate

rightside status my-app --json
rightside logs my-app --runtime
rightside rollback my-app
Completion rule. A successful local build is IMPLEMENTED. It is not DEPLOYED until the live URL and active release are verified.