Server Templates & Recipes

When scaling infrastructure, consistency is critical. If your staging server is configured differently than your production server, deployments will fail unpredictably.

Server Templates and Deployment Recipes allow you to standardize your infrastructure natively, without resorting to complex external IaC tools like Ansible or Terraform.

Deployment Recipes

A Deployment Recipe is a pre-defined set of instructions (Intents) that dictate how a server should be configured.

Instead of writing bash scripts, you can use the RasnuOS UI or the AI AutoPilot to generate a Recipe that defines:

• Which specific apt/yum packages to install.
• Which Docker containers should be running.
• The exact configuration of the local firewall (e.g., open port 80/443).
• Which GitHub repositories to pull and build.

Applying Templates at Provisioning

The true power of Server Templates is realized during Automated Provisioning.

When you spin up a new instance via the RasnuOS dashboard, you can attach a Deployment Recipe to the provisioning command.

1. The cloud provider boots the new server.
2. The RasnuOS Agent is injected via cloud-init and dials home.
3. The Control Plane detects the attached Template and immediately queues the Recipe.
4. The Agent executes the Recipe, installing all necessary databases, runtimes, and application code.

The server transitions from a raw OS image to a fully functional, production-ready application node in minutes—with absolutely zero manual intervention required.