Skip to content

Config Templates

The conf/ directory ships many ready-made templates — just cp conf/<x>.yml pigsty.yml and go.

Single-node templates

TemplateResourcesScenario
meta.yml1C / 2GMinimal sandbox
slim.yml1C / 2GPostgreSQL only, no monitoring
rich.yml4C / 8GSingle-node full feature
fat.yml8C / 16GSingle-node heavy load
infra.ymlINFRA components only
vibe.ymlAI development sandbox

HA templates

TemplateNodesNotes
trio.yml3Baseline HA
dual.yml2Primary + standby (no quorum)
full.yml4+Full production
safe.ymlCross-DCStrong consistency / sync repl
simu.ymlSimulationFailure drills

Kernel variants

TemplateKernel
pgsql.ymlNative PostgreSQL
citus.ymlCitus distributed
mssql.ymlMSSQL compatibility
polar.ymlPolarDB
agens.ymlAgensGraph

Application templates

conf/app/ contains ready-to-run Compose files for common open-source apps:

  • Supabase, Metabase, Superset
  • Odoo, NocoDB, Directus
  • Dify, Langfuse, Mastra
  • Gitea, Harbor, Keycloak

Full list: /docs/app/ and /docs/conf/

How to choose

text
How many hosts?
├── 1 → meta / rich / fat / slim
├── 2 → dual
├── 3 → trio  (recommended starting point)
└── 4+ → full / safe

Then decide whether to swap the kernel (citus / polar / mssql) or stack an application template (app/*.yml).

Released under the AGPL 3.0 License