Version v3.7.0 of the documentation is no longer actively maintained. The site that you are currently viewing is an archived snapshot. For up-to-date documentation, see the latest version.
Configuration
Pigsty treats Infra & Database as Code. You can describe everything with declarative config Inventory.
Which is usually an Ansible Inventory in YAML format: pigsty.yml.
But CMDB can also be used as dynamic inventory.
The configure procedure will generate a config according to your environment and input.
But it’s OPTIONAL: you can always edit the pigsty.yml file directly as tutorial shows.
And there are plenty of templates for your reference.
The main config file of Pigsty, Describe your entire deployment
Generate config file according to your input & environment
Planning your deployment according to business requirements
Available configuration templates and examples
Security considerations and best practices for prod deployment
Use PostgreSQL as CMDB instead of local YAML config file
PostgreSQL Cluster with HA, PITR, IaC, ACL, Monitoring, Pooling
Nginx, Repo, DNS, NTP, Prometheus and Grafana stack for Observability
Enroll nodes into the desired state and monitor it, and VIP, HAProxy
Reliable distributed consensus storage (DCS), empowering PGSQL HA
S3 compatible object storage, optional backup storage
High-performance in-memory cache, optional data structure server
The main config file for Pigsty
how to configure pigsty inventory file?
Forge a complex config from scratch
Configuration templates for Pigsty
Security considerations and best-practices
Use PostgreSQL as config inventory