add supabase asciinema demo

Author: Vonng

content/docs/app/supabase.md

@@ -1,8 +1,7 @@
 ---
 title: "Enterprise Self-Hosted Supabase"
 weight: 555
-date: 2024-11-30
-description: Self-host enterprise-grade Supabase with Pigsty, featuring monitoring, high availability, PITR, IaC, and 400+ PostgreSQL extensions.
+description: Self-host enterprise-grade Supabase with Pigsty, featuring monitoring, high availability, PITR, IaC, and 440+ PostgreSQL extensions.
 module: [SOFTWARE]
 categories: [Reference]
 ---
@@ -17,10 +16,10 @@ Pigsty can help you deploy enterprise-grade Supabase on your own servers (physic
 
 ## TL;DR
 
-[Prepare](/docs/deploy/prepare) a [Linux](/docs/deploy/prepare) server, follow the Pigsty [standard installation](/docs/setup/install) process with the `supabase` configuration template:
+[Prepare](/docs/deploy/prepare) a [**Linux**](/docs/deploy/prepare) server, follow the Pigsty [standard installation](/docs/setup/install) process with the `supabase` configuration template:
 
 ```bash
-curl -fsSL https://repo.pigsty.io/get | bash; cd ~/pigsty
+curl -fsSL https://repo.pigsty.cc/get | bash; cd ~/pigsty
 ./configure -c supabase    # Use supabase config (change credentials in pigsty.yml)
 vi pigsty.yml              # Edit domain, passwords, keys...
 ./deploy.yml               # Install Pigsty
@@ -32,6 +31,11 @@ After installation, access Supa Studio on port `8000` with username `supabase` a
 
 ![](/img/docs/supabase-login.png)
 
+{{< asciinema file="demo/supabase.cast" markers="0:Check,11:Install,43:Config,307:Docker,321:Domain,340:App,350:Verify" theme="solarized-light" speed="1.3" autoplay="true" loop="true" >}}
+
+
+
+
 ------
 
 ## Table of Contents
@@ -56,7 +60,7 @@ Supabase aims to provide developers with a one-stop backend solution, reducing t
 It allows developers to skip most backend development work — **you only need to understand database design and frontend to ship quickly!**
 Developers can use vibe coding to create a frontend and database schema to rapidly build complete applications.
 
-Currently, Supabase is the most popular open-source project in the [PostgreSQL ecosystem](https://ossrank.com/cat/368-postgresql-ecosystem), with over [80,000](https://github.com/supabase/supabase/) GitHub stars.
+Currently, Supabase is the most popular open-source project in the [PostgreSQL ecosystem](https://ossrank.com/cat/368-postgresql-ecosystem), with over [90,000](https://github.com/supabase/supabase/) GitHub stars.
 Supabase also offers a "generous" free tier for small startups — free 500 MB storage, more than enough for storing user tables and analytics data.
 
 ------
@@ -65,18 +69,18 @@ Supabase also offers a "generous" free tier for small startups — free 500 MB s
 
 If Supabase cloud is so attractive, why self-host?
 
-The most obvious reason is what we discussed in "[Is Cloud Database an IQ Tax?](https://blog.vonng.com/cloud/rds/)": when your data/compute scale exceeds the cloud computing sweet spot (Supabase: 4C/8G/500MB free storage), costs can explode.
-And nowadays, reliable [local enterprise NVMe SSDs](https://blog.vonng.com/cloud/bonus/) have three to four orders of magnitude cost advantage over [cloud storage](https://blog.vonng.com/cloud/ebs/), and self-hosting can better leverage this.
+The most obvious reason is what we discussed in "[Is Cloud Database an IQ Tax?](https://vonng.com/cloud/rds/)": when your data/compute scale exceeds the cloud computing sweet spot (Supabase: 4C/8G/500MB free storage), costs can explode.
+And nowadays, reliable [local enterprise NVMe SSDs](https://vonng.com/cloud/bonus/) have three to four orders of magnitude cost advantage over [cloud storage](https://vonng.com/cloud/ebs/), and self-hosting can better leverage this.
 
 Another important reason is **functionality** — Supabase cloud features are limited. Many powerful PostgreSQL extensions aren't available in cloud services due to multi-tenant security challenges and licensing.
-Despite [extensions being PostgreSQL's core feature](https://blog.vonng.com/pg/pg-eat-db-world), only **64** extensions are available on Supabase cloud.
-Self-hosted Supabase with Pigsty provides up to [**437**](https://pgext.cloud/list) ready-to-use PostgreSQL extensions.
+Despite [extensions being PostgreSQL's core feature](https://vonng.com/pg/pg-eat-db-world), only **64** extensions are available on Supabase cloud.
+Self-hosted Supabase with Pigsty provides up to [**440**](https://pgext.cloud/list) ready-to-use PostgreSQL extensions.
 
 Additionally, self-control and vendor lock-in avoidance are important reasons for self-hosting. Although Supabase aims to provide a vendor-lock-free open-source Google Firebase alternative, self-hosting enterprise-grade Supabase is not trivial.
-Supabase includes a series of PostgreSQL extensions they develop and maintain, and plans to replace the native PostgreSQL kernel with [OrioleDB](/docs/pgsql/kernel/orioledb) (which they acquired). These kernels and extensions are not available in the official PGDG repository.
+Supabase includes a series of PostgreSQL extensions they develop and maintain, and plans to replace the native PostgreSQL kernel with [**OrioleDB**](/docs/pgsql/kernel/orioledb) (which they acquired). These kernels and extensions are not available in the official PGDG repository.
 
 This is implicit vendor lock-in, preventing users from self-hosting in ways other than the supabase/postgres Docker image. Pigsty provides an open, transparent, and universal solution.
-We package all 10 missing Supabase extensions into ready-to-use RPM/DEB packages, ensuring they work on all [major Linux distributions](/docs/deploy/prepare):
+We package all 10 missing Supabase extensions into ready-to-use RPM/DEB packages, ensuring they work on all [major Linux distributions](/docs/ref/linux):
 
 | Extension | Description |
 |---|---|
@@ -108,7 +112,7 @@ Let's start with single-node Supabase deployment. We'll cover multi-node high av
 then run [`docker.yml`](/docs/docker/playbook#dockeryml) and `app.yml` to start stateless Supabase containers (default ports `8000`/`8433`).
 
 ```bash
-curl -fsSL https://repo.pigsty.io/get | bash; cd ~/pigsty
+curl -fsSL https://repo.pigsty.cc/get | bash; cd ~/pigsty
 ./configure -c supabase    # Use supabase config (change credentials in pigsty.yml)
 vi pigsty.yml              # Edit domain, passwords, keys...
 ./deploy.yml               # Install Pigsty
@@ -119,16 +123,15 @@ vi pigsty.yml              # Edit domain, passwords, keys...
 Before deploying Supabase, modify the auto-generated `pigsty.yml` configuration file (domain and passwords) according to your needs.
 For local development/testing, you can skip this and customize later.
 
-{{< asciinema src="/img/asciinema/supabase.svg" poster="npt:2:24" >}}
-
 If configured correctly, after about ten minutes, you can access the Supabase Studio GUI at `http://<your_ip_address>:8000` on your local network.
 Default username and password are `supabase` and `pigsty`.
 
 ![](/img/docs/supabase-home.png)
 
 **Notes:**
 
-- In mainland China, Pigsty uses 1Panel and 1ms DockerHub mirrors by default, which may be slow. You can configure your own [proxy](/docs/docker/param#proxy) and [registry mirror](/docs/docker/param#registry), then manually pull images with `cd /opt/supabase; docker compose pull`. We also offer expert consulting services including complete offline installation packages.
+- In mainland China, Pigsty uses 1Panel and 1ms DockerHub mirrors by default, which may be slow.
+- You can configure your own [proxy](/docs/docker/usage#proxy) and [registry mirror](/docs/docker/usage#registry-mirror), then manually pull images with `cd /opt/supabase; docker compose pull`. We also offer expert consulting services including complete offline installation packages.
 - If you need object storage functionality, you must access Supabase via domain and HTTPS, otherwise errors will occur.
 - For serious production deployments, **always** change all default passwords!
 
@@ -147,7 +150,8 @@ However, single-node deployment still has significant advantages over the offici
 If you only have one server or choose to self-host on cloud servers, Pigsty recommends using external S3 instead of local MinIO for object storage to hold PostgreSQL backups and Supabase Storage.
 This deployment provides a minimum safety net RTO (hour-level recovery time) / RPO (MB-level data loss) disaster recovery in single-node conditions.
 
-For serious production deployments, Pigsty recommends at least 3-4 nodes, ensuring both MinIO and PostgreSQL use enterprise-grade multi-node high availability deployments. You'll need more nodes and disks, adjusting cluster configuration in `pigsty.yml` and Supabase cluster configuration to use high availability endpoints.
+For serious production deployments, Pigsty recommends at least 3-4 nodes, ensuring both MinIO and PostgreSQL use enterprise-grade multi-node high availability deployments.
+You'll need more nodes and disks, adjusting cluster configuration in `pigsty.yml` and Supabase cluster configuration to use high availability endpoints.
 
 Some Supabase features require sending emails, so SMTP service is needed. Unless purely for internal use, production deployments should use SMTP cloud services. Self-hosted mail servers' emails are often marked as spam.
 
@@ -171,7 +175,8 @@ For serious production deployments, we strongly recommend changing Pigsty compon
 - [`patroni_password`](/docs/pgsql/param/#patroni_password): `Patroni.API`, Patroni HA component password
 - [`haproxy_admin_password`](/docs/node/param/#haproxy_admin_password): `pigsty`, Load balancer admin password
 - [`minio_secret_key`](/docs/minio/param/#minio_secret_key): `S3User.MinIO`, MinIO root user secret
-- Additionally, strongly recommend changing the [PostgreSQL business user](https://github.com/pgsty/pigsty/blob/main/conf/supabase.yml#L68) password for Supabase, default is `DBUser.Supa`
+- [`etcd_root_password`](/docs/etcd/param/#etcd_root_password): `Etcd.Root`, ETCD root user password
+- Additionally, strongly recommend changing the [PostgreSQL business user](https://github.com/pgsty/pigsty/blob/main/conf/supabase.yml#L72) password for Supabase, default is `DBUser.Supa`
 
 These are Pigsty component passwords. Strongly recommended to set before installation.
 
@@ -221,7 +226,6 @@ sed -ie 's/supa.pigsty/supa.pigsty.cc/g' ~/pigsty/pigsty.yml
 If not configured beforehand, reload Nginx and Supabase configuration:
 
 ```bash
-make nginx      # Reload nginx configuration
 make cert       # Request certbot free HTTPS certificate
 ./app.yml       # Reload Supabase configuration
 ```
@@ -231,7 +235,9 @@ The modified configuration should look like:
 ```yaml
 all:
   vars:
+    certbot_sign: true                # Use certbot to sign real certificates
     infra_portal:
+      home: i.pigsty.cc               # Replace with your domain!
       supa:
         domain: supa.pigsty.cc        # Replace with your domain!
         endpoint: "10.10.10.10:8000"
@@ -251,7 +257,6 @@ all:
 
 For complete domain/HTTPS configuration, see [Certificate Management](/docs/infra/admin/cert). You can also use Pigsty's built-in local static resolution and self-signed HTTPS certificates as fallback.
 
-{{< asciinema src="/img/asciinema/supa-domain.svg" poster="npt:2:24" >}}
 
 
 
@@ -261,7 +266,7 @@ For complete domain/HTTPS configuration, see [Certificate Management](/docs/infr
 
 You can use S3 or S3-compatible services for PostgreSQL backups and Supabase object storage. Here we use Alibaba Cloud OSS as an example.
 
-> Pigsty provides a [`terraform/spec/aliyun-meta-s3.tf`](https://github.com/pgsty/pigsty/blob/main/terraform/spec/aliyun-meta-s3.tf) template for provisioning a server and OSS bucket on Alibaba Cloud.
+> Pigsty provides a [`terraform/spec/aliyun-s3.tf`](https://github.com/pgsty/pigsty/blob/main/terraform/spec/aliyun-s3.tf) template for provisioning a server and OSS bucket on Alibaba Cloud.
 
 First, modify the S3 configuration in `all.children.supa.vars.apps.[supabase].conf` to point to Alibaba Cloud OSS:
 

content/docs/conf/supabase.md

@@ -37,6 +37,12 @@ Source: [`pigsty/conf/supabase.yml`](https://github.com/pgsty/pigsty/blob/main/c
 
 {{< readfile file="yaml/supabase.yml" code="true" lang="yaml" >}}
 
+--------
+
+## Installation Demo
+
+{{< asciinema file="demo/supabase.cast" markers="0:Check,11:Install,43:Config,307:Docker,321:Domain,340:App,350:Verify" theme="solarized-light" speed="1.3" autoplay="true" loop="true" >}}
+
 
 --------
 

content/docs/pgsql/kernel/supabase.md

@@ -53,7 +53,8 @@ then access `https://supa.pigsty` through a browser to enter the Supabase Studio
 
 > Default username and password: supabase / pigsty
 
-[![asciicast](https://asciinema.org/a/692194.svg)](https://asciinema.org/a/692194)
+{{< asciinema file="demo/supabase.cast" markers="0:Check,11:Install,43:Config,307:Docker,321:Domain,340:App,350:Verify" theme="solarized-light" speed="1.3" autoplay="true" loop="true" >}}
+
 
 
 -------