Services and queues

Use this pattern when backend processes need local infrastructure before they start: databases, object storage, vector storage, Redis, and RabbitMQ queues.

schema_version = 1
tld = "local.dev.test"

enabled = [
  "mongodb",
  "rabbitmq",
  "redis",
  "minio",
  "qdrant",
]

[[rabbitmq.vhost]]
name = "platform"
queues = [
  "jobs.default",
  "jobs.priority",
  "events.outbox",
]

What this generates

vectron stack provision validates the source file, prepares plugin assets, and generates the derived vectron.toml used by vectron start.

The service plugins in this example do not need dedicated configuration sections. rabbitmq does: when enabled, it requires at least one [[rabbitmq.vhost]] entry.

What to customize

• enabled: keep only the services your workspace actually needs.
• rabbitmq.vhost.name: use the vhost name expected by your application.
• queues: keep the list close to your project conventions, but avoid publishing internal queue names in public examples.

For exact ports, credentials, and generated process behavior, use the vectron.stack.toml reference and the generated files under .vectron_stack/.