Guides
Step by step, from a docker-compose.yml on your machine to an app running on OmniArc, with a branch of it. Start with Get started: a few minutes, one small shop, and a full copy of it with its data.
Every guide uses the same example, a shop with a JSON API over Postgres, and the panel beside it shows the shop's files.
- Get startedInstall the CLI, deploy a small shop with its database, then branch it: a full copy of the app and its data.
- The modelArcs, branches and services, and why your compose file needs only one file beside it.
- Write arc.yamlFrom a compose file to an arc.yaml, one decision at a time, with the shop as the example.
- DeployCheck your project on your machine, deploy it with one command, follow it, and redeploy an earlier revision.
- BranchesA full copy of the app and its data in one command: for a pull request, a migration rehearsal, or a demo.
- Env and secretsOne .env per arc, shared by every branch, set from the CLI and never printed back.
- DomainsServe a branch at a domain you own, with its certificate issued for you.
- Sleep and wakeStop a branch you are not using and keep its data, and choose how long an unused arc is kept.
- CostsWhat is measured, what it costs so far this month, and how to keep it down.