Deployment Runs & Rollbacks

Deploying application code securely and predictably is the primary job of any infrastructure platform. RasnuOS tracks every single deployment as an immutable record, ensuring complete traceability and instant rollback capabilities.

The Deployment Lifecycle

When you trigger a deployment — either manually via the dashboard or automatically via a Webhook — RasnuOS initiates a strict lifecycle:

1. Intent Generation: The Control Plane generates a cryptographic payload detailing the exact Git repository, branch, and commit hash to pull. This payload is signed and transmitted down the mTLS tunnel to the Agent.
2. Agent Execution: The Agent receives the intent and runs your configured build script. This could be go build ./..., npm ci && npm run build, cargo build --release, bundle install, or any other build command your stack requires.
3. Live Log Streaming: Every line of stdout from the build process is streamed in real-time over a secure WebSocket back to your browser. You watch the build progress line-by-line without needing SSH access.
4. Zero-Downtime Reload: Once the build completes successfully, the Agent gracefully signals the running application process to reload. No in-flight HTTP requests are dropped. The application is continuously available throughout the entire process.

Webhooks & CI/CD Integration

You can wire RasnuOS directly into your existing CI/CD pipelines on GitHub Actions, GitLab CI, Bitbucket Pipelines, or CircleCI.

By generating an Inbound Webhook URL for a specific Server Group, your pipeline can trigger a RasnuOS deployment the exact second your automated test suite passes. You stop manually deploying and start trusting the automation.

1-Click Rollbacks

If a deployment introduces a critical bug into production, speed is the only metric that matters. You do not have time to run a git revert, wait for the CI pipeline to rebuild assets, and manually push to the server.

Because RasnuOS maintains an immutable, chronological history of every deployment — recording the exact Git commit hash — rolling back is instantaneous.

You click Rollback on any previous successful deployment in the history list. The Control Plane immediately commands the Agent to restore the application directory to that exact commit state and gracefully reload the service. Your downtime is measured in seconds.