Skip to content

Commit 5535c22

Browse files
VonngVonng
committed
fix some legacy commands
1 parent 6b8b468 commit 5535c22

File tree

23 files changed

+62
-62
lines changed

23 files changed

+62
-62
lines changed

‎content/blog/db/supabase.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ First, download & [install](/docs/setup/install) pigsty as usual, with the `supa
7373
curl -fsSL https://repo.pigsty.io/get | bash
7474
./bootstrap # install deps (ansible)
7575
./configure -c supa # use supa config template (IMPORTANT: CHANGE PASSWORDS!)
76-
./install.yml # install pigsty, create ha postgres & minio clusters
76+
./deploy.yml # install pigsty, create ha postgres & minio clusters
7777
```
7878

7979
> Please change the `pigsty.yml` config file according to your need before deploying Supabase. (**Credentials**)

‎content/docs/about/license.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ For PostgreSQL extension plugin licenses, refer to [**PostgreSQL Extension Licen
9999
| PGSQL | [pgbackrest](https://pgbackrest.org/) | [MIT License](https://github.com/pgbackrest/pgbackrest/blob/main/LICENSE) | PITR backup/recovery management | **Recommended** |
100100
| PGSQL | [pgbouncer](https://www.pgbouncer.org/community.html) | [ISC License](https://github.com/pgbouncer/pgbouncer/blob/master/COPYRIGHT) | PostgreSQL connection pooling | **Recommended** |
101101
| PGSQL | [vip-manager](https://github.com/cybertec-postgresql/vip-manager) | [BSD 2-Clause License](https://github.com/cybertec-postgresql/vip-manager/blob/master/LICENSE) | Automatic L2 VIP binding to PG primary | **Recommended** |
102-
| PGSQL | [pg_exporter](https://github.com/Vonng/pg_exporter) | [Apache License 2.0](https://github.com/Vonng/pg_exporter/blob/master/LICENSE) | PostgreSQL and PgBouncer monitoring | **Recommended** |
102+
| PGSQL | [pg_exporter](https://github.com/pgsty/pg_exporter) | [Apache License 2.0](https://github.com/pgsty/pg_exporter/blob/master/LICENSE) | PostgreSQL and PgBouncer monitoring | **Recommended** |
103103
| NODE | [node_exporter](https://github.com/prometheus/node_exporter) | [Apache License 2.0](https://github.com/prometheus/node_exporter/blob/master/LICENSE) | Host node monitoring metrics | **Recommended** |
104104
| NODE | [haproxy](https://www.haproxy.org/) | [HAPROXY's License](https://www.haproxy.org/download/1.3/doc/LICENSE) (GPLv2) | Load balancing and service exposure | **Recommended** |
105105
| INFRA | [Grafana](https://grafana.com/) | [AGPLv3](https://github.com/grafana/grafana/blob/main/LICENSE) | Database visualization platform | **Recommended** |

‎content/docs/about/release.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -342,7 +342,7 @@ cc022ea89181d89d271a9aaabca04165 pigsty-pkg-v3.7.0.u22.x86_64.tgz
342342
## v3.6.1
343343

344344
```bash
345-
curl https://repo.pigsty.cc/get | bash -s v3.6.1
345+
curl https://repo.pigsty.io/get | bash -s v3.6.1
346346
```
347347

348348
**Highlights**
@@ -401,7 +401,7 @@ c25ccfb98840c01eb7a6e18803de55bb pigsty-pkg-v3.6.1.u22.x86_64.tgz
401401
## v3.6.0
402402

403403
```bash
404-
curl https://repo.pigsty.cc/get | bash -s v3.6.0
404+
curl https://repo.pigsty.io/get | bash -s v3.6.0
405405
```
406406

407407
**Highlights**

‎content/docs/app/_index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ And Pigsty just have a series of Docker Compose templates for these software, ap
4444
| [**pgWeb**](pgweb) | [pgWeb](https://github.com/sosedoff/pgweb?tab=readme-ov-file) | TOOL | **GA** | 8886 | cli.pigsty | PostgreSQL Web GUI Client |
4545
| SchemaSpy | [SchemaSpy](https://schemaspy.org/) | TOOL | *TBD* | | | Dump & Visualize PostgreSQL Schema |
4646
| pgBadger | [pgBadger](https://github.com/darold/pgbadger) | TOOL | *TBD* | | | PostgreSQL Log Analysis |
47-
| pg_exporter | [pg_exporter](https://github.com/Vonng/pg_exporter) | TOOL | **GA** | 9630 | | Expose PostgreSQL & Pgbouncer Metrics for Prometheus |
47+
| pg_exporter | [pg_exporter](https://github.com/pgsty/pg_exporter) | TOOL | **GA** | 9630 | | Expose PostgreSQL & Pgbouncer Metrics for Prometheus |
4848

4949

5050
{{% alert title="How to prepare Docker?" color="success" %}}

‎content/docs/concept/arch/pgsql.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -311,7 +311,7 @@ For more information, see: [**Tutorial: VIP Configuration**](/docs/pgsql/tutoria
311311

312312
## pg_exporter
313313

314-
[**pg_exporter**](https://github.com/Vonng/pg_exporter) exports [PostgreSQL](#postgresql) monitoring metrics, listening on port `9630` by default.
314+
[**pg_exporter**](https://github.com/pgsty/pg_exporter) exports [PostgreSQL](#postgresql) monitoring metrics, listening on port `9630` by default.
315315

316316
**pg_exporter** runs on each PG node, connecting to [**PostgreSQL**](#postgresql) via local Unix socket,
317317
exporting rich metrics covering sessions, buffer hits, replication lag, transaction rates, etc., scraped by **VictoriaMetrics** on INFRA nodes.

‎content/docs/concept/sec/ca.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ files/pki/ca/ca.key # Core CA private key file, must exist; if missing, a ne
4545
files/pki/ca/ca.crt # If certificate file is missing, Pigsty auto-generates a new root certificate from the CA private key
4646
```
4747

48-
When Pigsty executes the [**`install.yml`**](/docs/infra/#installyml) or [**`infra.yml`**](/docs/infra/#infrayml) playbooks, if a `ca.key` private key file exists in `files/pki/ca`, the existing CA will be used. Since `ca.crt` can be generated from the `ca.key` private key, Pigsty will automatically regenerate the root certificate file if it's missing.
48+
When Pigsty executes the [**`deploy.yml`**](/docs/infra/#installyml) or [**`infra.yml`**](/docs/infra/#infrayml) playbooks, if a `ca.key` private key file exists in `files/pki/ca`, the existing CA will be used. Since `ca.crt` can be generated from the `ca.key` private key, Pigsty will automatically regenerate the root certificate file if it's missing.
4949

5050
{{% alert title="Note When Using Existing CA" color="secondary" %}}
5151
You can set the [**`ca_method`**](/docs/infra/param#ca_method) parameter to `copy` to ensure Pigsty errors out and stops if it can't find a local CA, rather than auto-generating a new self-signed CA.

‎content/docs/deploy/install.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ install a [**compatible Linux OS**](/docs/ref/linux/), then execute with an [**a
2020

2121
```bash
2222
curl -fsSL https://repo.pigsty.io/get | bash; # International
23-
curl -fsSL https://repo.pigsty.cc/get | bash; # China Mirror
23+
curl -fsSL https://repo.pigsty.cc/get | bash; # Backup Mirror
2424
```
2525

2626
This runs the [**install**](#install) script, downloading and extracting Pigsty source to your home directory with dependencies installed. Complete [**configuration**](#configure) and [**deployment**](#deploy) to finish.
@@ -73,7 +73,7 @@ Use the following to automatically install the [**Pigsty source package**](/docs
7373

7474
```bash
7575
curl -fsSL https://repo.pigsty.io/get | bash # Install latest stable version
76-
curl -fsSL https://repo.pigsty.cc/get | bash # China mirror
76+
curl -fsSL https://repo.pigsty.cc/get | bash # Backup mirror
7777
curl -fsSL https://repo.pigsty.io/get | bash -s v4.0.0 # Install specific version
7878
```
7979

‎content/docs/deploy/prepare.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@ You can [**install**](/docs/deploy/install#install) the latest stable Pigsty sou
188188

189189
```bash
190190
curl -fsSL https://repo.pigsty.io/get | bash; # International
191-
curl -fsSL https://repo.pigsty.cc/get | bash; # China Mirror
191+
curl -fsSL https://repo.pigsty.cc/get | bash; # Backup Mirror
192192
```
193193

194194
To [**install**](/docs/deploy/install#install) a specific version, use the **`-s <version>`** parameter:

‎content/docs/docker/usage.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ repo_extra_packages:
9696
- pgsql-main docker # <--- Can also be specified here
9797
```
9898

99-
The `docker` specified here (which actually corresponds to the `docker-ce` and `docker-compose-plugin` packages) will be automatically downloaded to the local repository during the default [`install.yml`](/docs/setup/playbook#installyml) process.
99+
The `docker` specified here (which actually corresponds to the `docker-ce` and `docker-compose-plugin` packages) will be automatically downloaded to the local repository during the default [`deploy.yml`](/docs/setup/playbook#installyml) process.
100100
After downloading, the Docker packages will be available to all nodes via the local repository.
101101

102102
If you've already completed Pigsty installation and the local repository is initialized, you can run `./infra.yml -t repo_build` after modifying the configuration to re-download and rebuild the offline repository.

‎content/docs/infra/admin/playbook.md‎

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -11,39 +11,39 @@ Pigsty uses **idempotent** Ansible playbooks for management and control. Running
1111

1212
## Available Playbooks
1313

14-
| Module | Playbook | Purpose |
15-
|--------|-----------------------|------------------------------------------------------|
16-
| INFRA | `install.yml` | One-click Pigsty installation |
17-
| INFRA | `infra.yml` | Initialize Pigsty infrastructure on infra nodes |
18-
| INFRA | `infra-rm.yml` | Remove infrastructure components from infra nodes |
14+
| Module | Playbook | Purpose |
15+
|--------|-----------------------|--------------------------------------------------------|
16+
| INFRA | `deploy.yml` | One-click Pigsty installation |
17+
| INFRA | `infra.yml` | Initialize Pigsty infrastructure on infra nodes |
18+
| INFRA | `infra-rm.yml` | Remove infrastructure components from infra nodes |
1919
| INFRA | `cache.yml` | Create offline installation packages from target nodes |
20-
| INFRA | `cert.yml` | Issue certificates using Pigsty self-signed CA |
21-
| NODE | `node.yml` | Initialize nodes, configure to desired state |
22-
| NODE | `node-rm.yml` | Remove nodes from Pigsty |
23-
| PGSQL | `pgsql.yml` | Initialize HA PostgreSQL cluster, or add new replica |
24-
| PGSQL | `pgsql-rm.yml` | Remove PostgreSQL cluster, or remove replica |
25-
| PGSQL | `pgsql-db.yml` | Add new business database to existing cluster |
26-
| PGSQL | `pgsql-user.yml` | Add new business user to existing cluster |
27-
| PGSQL | `pgsql-pitr.yml` | Perform point-in-time recovery (PITR) on cluster |
28-
| PGSQL | `pgsql-monitor.yml` | Monitor remote PostgreSQL using local exporters |
29-
| PGSQL | `pgsql-migration.yml` | Generate migration manual and scripts for PostgreSQL |
30-
| PGSQL | `slim.yml` | Install Pigsty with minimal components |
31-
| REDIS | `redis.yml` | Initialize Redis cluster/node/instance |
32-
| REDIS | `redis-rm.yml` | Remove Redis cluster/node/instance |
33-
| ETCD | `etcd.yml` | Initialize ETCD cluster, or add new member |
34-
| ETCD | `etcd-rm.yml` | Remove ETCD cluster, or remove existing member |
35-
| MINIO | `minio.yml` | Initialize MinIO cluster |
36-
| MINIO | `minio-rm.yml` | Remove MinIO cluster |
37-
| DOCKER | `docker.yml` | Install Docker on nodes |
38-
| DOCKER | `app.yml` | Install applications using Docker Compose |
39-
| FERRET | `mongo.yml` | Install Mongo/FerretDB on nodes |
20+
| INFRA | `cert.yml` | Issue certificates using Pigsty self-signed CA |
21+
| NODE | `node.yml` | Initialize nodes, configure to desired state |
22+
| NODE | `node-rm.yml` | Remove nodes from Pigsty |
23+
| PGSQL | `pgsql.yml` | Initialize HA PostgreSQL cluster, or add new replica |
24+
| PGSQL | `pgsql-rm.yml` | Remove PostgreSQL cluster, or remove replica |
25+
| PGSQL | `pgsql-db.yml` | Add new business database to existing cluster |
26+
| PGSQL | `pgsql-user.yml` | Add new business user to existing cluster |
27+
| PGSQL | `pgsql-pitr.yml` | Perform point-in-time recovery (PITR) on cluster |
28+
| PGSQL | `pgsql-monitor.yml` | Monitor remote PostgreSQL using local exporters |
29+
| PGSQL | `pgsql-migration.yml` | Generate migration manual and scripts for PostgreSQL |
30+
| PGSQL | `slim.yml` | Install Pigsty with minimal components |
31+
| REDIS | `redis.yml` | Initialize Redis cluster/node/instance |
32+
| REDIS | `redis-rm.yml` | Remove Redis cluster/node/instance |
33+
| ETCD | `etcd.yml` | Initialize ETCD cluster, or add new member |
34+
| ETCD | `etcd-rm.yml` | Remove ETCD cluster, or remove existing member |
35+
| MINIO | `minio.yml` | Initialize MinIO cluster |
36+
| MINIO | `minio-rm.yml` | Remove MinIO cluster |
37+
| DOCKER | `docker.yml` | Install Docker on nodes |
38+
| DOCKER | `app.yml` | Install applications using Docker Compose |
39+
| FERRET | `mongo.yml` | Install Mongo/FerretDB on nodes |
4040

4141

4242
----------------
4343

4444
## Deployment Strategy
4545

46-
The `install.yml` playbook orchestrates specialized playbooks in the following group order for complete deployment:
46+
The `deploy.yml` playbook orchestrates specialized playbooks in the following group order for complete deployment:
4747

4848
- **infra**: `infra.yml` (-l infra)
4949
- **nodes**: `node.yml`
@@ -52,7 +52,7 @@ The `install.yml` playbook orchestrates specialized playbooks in the following g
5252
- **pgsql**: `pgsql.yml`
5353

5454
> **Circular Dependency Note**: There is a weak circular dependency between NODE and INFRA: to register NODE to INFRA, INFRA must already exist; while INFRA module depends on NODE to work.
55-
> The solution is to initialize `infra` nodes first, then add other nodes. To complete all deployment at once, use `install.yml`.
55+
> The solution is to initialize `infra` nodes first, then add other nodes. To complete all deployment at once, use `deploy.yml`.
5656
5757

5858
----------------

0 commit comments

Comments
 (0)