# Configuration Template

This directory (`files/pigsty`) contains pigsty config templates,
Which will be used during [`configure`](https://doc.pigsty.cc/#/INSTALL) procedure.

Config templates are named as `<mode>.yml`.  `<mode>` can be designated using `./configure -m <mode>`

There are several built-in templates:

* [full.yml](full.yml) : detail documented config example with default parameters
* [demo.yml](demo.yml) : exact same as default.yml, in short version
* [auto.yml](auto.yml) : Pigsty auto generated config for el7,8,9 singleton
* [el7.yml](el7.yml) : If you wish to download packages from upstream directly on EL7
* [el8.yml](el8.yml) : If you wish to download packages from upstream directly on EL8
* [el8.yml](el8.yml) : If you wish to download packages from upstream directly on EL9
* [prod.yml](prod.yml) : Production emulated config with 42 nodes and 71C
* [security.yml](security.yml) : security enhanced config (on el7)
* [citus.yml](citus.yml) : citus cluster example: 1 coordinator and 3 data nodes
* [build.yml](build.yml) : 3 nodes el7, el8, el9 for release building
* [pubic.yml](public.yml) : config for [public demo](https://demo.pigsty.cc)
* [test.yml](test.yml) : config for different EL distribution testing
* [remote.yml](remote.yml) : example config for monitoring a remote pgsql cluster
* [dual.yml](dual.yml) : example config for a two node deployment
* [redis.yml](redis.yml) : example config for redis clusters
* [minio.yml](minio.yml) : example config for a 3-node minio clusters
* [uel20.yml](uel20.yml) : uel20 1050e example config 



* If `-m <mode>` is specified, corresponding `<mode>.yml` is used, otherwise:
* If offline package exists, `auto.yml` is used by default.
* If offline package not exists,  `el7.yml`, `el8.yml`, `el9.yml` are used according to the OS version. 

The `configure` procedure is optional. You can always skip it and create `pigsty.yml` by yourself. 