Documentation
Stack examples
Concrete `vectron.stack.toml` patterns for local development stacks.
These stack examples show realistic vectron.stack.toml source configurations. They sit between the stack guides and the vectron.stack.toml reference.
The examples are derived from real local platform patterns, then reduced and anonymized. They are not dumps of internal project configuration.
Stack mode is currently macOS-only. See the platform note before using these examples on a team.
Pick a starting point
| Example | Use it when |
|---|---|
| Reverse proxy and local DNS | You want local HTTPS hostnames in front of web and API processes |
| Services and queues | You need local datastores and RabbitMQ provisioning |
| Observability and Docker logs | You want Prometheus, Loki, Alloy, Grafana, and Docker log ingestion |
| Kubernetes local cluster | You want an explicit local Kubernetes cluster configuration |
| Full local platform | You want a compact end-to-end stack combining the common pieces |
How to use these examples
Start from the smallest example that matches your need, then add plugins incrementally. Validate each step with:
vectron stack check
vectron stack provision --dry-run
vectron stack provision
vectron startThe examples show the source vectron.stack.toml. vectron stack provision then generates the derived vectron.toml and plugin assets under .vectron_stack/.
What not to copy blindly
Replace domains, ports, queue names, dashboard paths, scrape config paths, and Docker labels with your project conventions. For exact field defaults and validation rules, use the vectron.stack.toml reference.
If you are looking for process orchestration examples for vectron.toml, use the Vectron examples.Pages in this section