# Orcra Run

## Docs

- [Managing environments with Git branches](https://docs.orcra.dev/concepts/environments.md): orun uses Git branches as environment boundaries. Each node tracks one branch, and Service domain templates resolve the correct hostname per environment.
- [How Orcra Run reconciles your containers](https://docs.orcra.dev/concepts/how-it-works.md): orun nodes poll your Git repository on a set interval, compare desired state to running containers, and apply changes autonomously — no push required.
- [Structuring your manifest repository](https://docs.orcra.dev/concepts/manifest-repository.md): Your Git repository is the only control plane orun has. Learn how nodes/, deployments/, and services/ map to the three resource kinds orun manages.
- [Deployment manifest: run containers with orun](https://docs.orcra.dev/configuration/deployment.md): All Deployment manifest fields: image vs. build mode, port bindings, health probes, volume mounts, environment variables, and SOPS-encrypted secrets.
- [Node manifest reference for orun](https://docs.orcra.dev/configuration/node.md): All fields in the Node manifest YAML: SSH connection details, Git repository URL, branch, poll interval, data directory, and local build code directory.
- [Encrypting secrets in your manifest repository](https://docs.orcra.dev/configuration/secrets.md): Commit SOPS-encrypted secrets directly to your manifest repository and let orun decrypt them at apply time using age keys stored only on each node.
- [Service manifest: expose deployments with ingress](https://docs.orcra.dev/configuration/service.md): Reference for the Service manifest, which links a Deployment to a domain name and enables automatic HTTPS via the Caddy server embedded in orun.
- [Bootstrap a server as an orun node over SSH](https://docs.orcra.dev/guides/bootstrap-a-node.md): Provision a remote Linux server as an orun node using orun bootstrap, covering prerequisites, interactive prompts, and what bootstrap does on the remote host.
- [Deploy a container application with Orcra Run](https://docs.orcra.dev/guides/deploy-your-first-app.md): Write a Deployment manifest, commit it to your manifest repository, and have orun pull and run the container on your node within seconds.
- [Build container images locally on your orun node](https://docs.orcra.dev/guides/local-image-builds.md): How to use orun build spec to build Docker images from source on the node, with build-once and watch modes explained for development and production workflows.
- [Monitor containers and view logs in orun](https://docs.orcra.dev/guides/monitoring-and-logs.md): How to view orun agent logs via journald, query the built-in status API for deployment health, and set up lightweight monitoring tools for containers.
- [Enable HTTPS ingress with automatic SSL in orun](https://docs.orcra.dev/guides/ssl-and-ingress.md): How to create a Service manifest to expose a Deployment on a custom domain with automatic TLS certificate provisioning via the embedded Caddy server.
- [Orcra Run: declarative containers via Git](https://docs.orcra.dev/introduction.md): Orcra Run is a pull-based container orchestrator with no control plane. Nodes read manifests from a Git repo and reconcile themselves — even airgapped.
- [Get started with Orcra Run](https://docs.orcra.dev/quickstart.md): Learn how to install orun, bootstrap your first node over SSH, and deploy a running container in minutes using a Git manifest repository.
- [orun CLI reference: bootstrap and start commands](https://docs.orcra.dev/reference/cli.md): Complete reference for the orun CLI: bootstrap to provision nodes over SSH, start to run the agent loop, and local to configure a development node.
- [orun Status API: node health and deployment state](https://docs.orcra.dev/reference/status-api.md): Reference for the orun HTTP status API on port 9100, including POST /status for full deployment reports and POST /healthz for liveness checks.
- [Troubleshooting common orun issues](https://docs.orcra.dev/reference/troubleshooting.md): Solutions to common orun problems including bootstrap failures, containers not starting, SSL issues, Git sync errors, and secrets decryption failures.