Add asf-staged for deployment preview

.asf.yaml

@@ -40,7 +40,6 @@ github:
     rebase: true
   protected_branches:
     asf-site: {}
-    asf-staging: {}
     main:
       required_status_checks:
         # strict means "Require branches to be up to date before merging".

.github/workflows/publish-cloudberry-site.yml

@@ -52,11 +52,29 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 20
-      - run: npm install
-      - run: npm run build
-      - run: cp .asf.yaml build/.asf.yaml
-      - uses: peaceiris/actions-gh-pages@v3
-        if: github.event_name != 'pull_request'
+
+      # Install dependencies and build site
+      - name: Install dependencies
+        run: npm install
+      - name: Build site
+        run: npm run build
+      - name: Copy ASF config
+        run: cp .asf.yaml build/.asf.yaml
+
+      # Deploy to asf-staging for PR preview
+      # You can view the staging site at https://cloudberry.staged.apache.org 
+      - name: Deploy to staging
+        if: github.event_name == 'pull_request'
+        uses: peaceiris/actions-gh-pages@v4
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          publish_dir: ./build
+          publish_branch: asf-staging
+
+      # Deploy to asf-site for production
+      - name: Deploy to production
+        if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+        uses: peaceiris/actions-gh-pages@v4
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
           publish_dir: ./build

docs/security/client-auth.md

@@ -4,7 +4,7 @@ title: Configure Client Authentication
 
 # Configure Client Authentication
 
-This topic explains how to configure client connections and authentication for Cloudberry Database.
+This topic explains how to configure client connections and authentication for Apache Cloudberry.
 
 When a Cloudberry Database system is first initialized, the system contains one predefined *superuser* role. This role will have the same name as the operating system user who initialized the Cloudberry Database system. This role is referred to as `gpadmin`. By default, the system is configured to only allow local connections to the database from the `gpadmin` role. If you want to allow any other roles to connect, or if you want to allow connections from remote hosts, you have to configure Cloudberry Database to allow such connections. This section explains how to configure client connections and authentication to Cloudberry Database.