add catalog-server deployment guide

Author: cyyeh

packages/doc/docs/deployment/flydotio.mdx

@@ -66,12 +66,12 @@ successfully logged in as xxxxx@xxx
 
 For more detailed introduction on how to sign in, you can [read more here](https://fly.io/docs/hands-on/sign-in/).
 
-## Step 3: Package your VulcanSQL project
+## Step 3: Package your VulcanSQL API Server
 
-In this guide, we'll deploy the Docker version of your VulcanSQL project. So please execute the following command in the terminal:
+In this guide, we'll deploy the Docker version of your VulcanSQL API Server. So please execute the following command in the terminal:
 
 ```bash
-vulcan package --output docker
+vulcan package -o docker
 ```
 
 After executing the command, you'll see a message shown like below and a new directory `dist` in the project directory.
@@ -163,7 +163,7 @@ For more detailed introduction on how to launch your app, you can [read more her
 
 ## Step 5: Deploy to Fly.io
 
-Finally, you can execute the following command in the terminal to deploy your VulcanSQL project and share it with the world!
+Finally, you can execute the following command in the terminal to deploy your VulcanSQL API Server and share it with the world!
 
 ```shell
 fly deploy
@@ -185,4 +185,30 @@ Congratulations! Now your VulcanSQL app is on the cloud and is ready to be share
 
 :::info
 If you need to clean up the resources on Fly.io, you can [read the documentation here](https://fly.io/docs/flyctl/destroy/).
-:::
+:::
+
+## Step 6: (Optional) Deploy your VulcanSQL API Catalog Server
+
+If you need to deploy API Catalog Server, you should execute the following command in the terminal:
+
+```shell
+vulcan package -t catalog-server -o docker
+```
+
+:::caution
+The folder generated by the command is also called `dist`, so if you had executed the command of packaging
+API server, you should rename the `dist` folder generated previously to prevent from being overwritten.
+:::
+
+Then, you should modify `API_BASE_URL` to the URL of your VulcanSQL API Server you just deployed in Dockerfile:
+
+```dockerfile
+ENV API_BASE_URL [URL of VulcanSQL API Server]
+```
+
+Finally, you execute the same Fly.io commands used in the step 4 and step 5 in the terminal, and change any configurations if you need:
+
+```
+fly launch
+fly deploy
+```

packages/doc/docs/deployment/gcp-app-engine.mdx

@@ -25,9 +25,9 @@ Before you begin to use Cloud Run on GCP, you need to do several things:
 
 For more detailed instructions on how to setup the environment, you can [read more here](https://cloud.google.com/appengine/docs/standard/nodejs/building-app/creating-project).
 
-## Step 2: Package your VulcanSQL project
+## Step 2: Package your VulcanSQL API Server
 
-In this guide, we'll deploy your VulcanSQL project without Docker. So please execute the following command in the terminal:
+In this guide, we'll deploy your VulcanSQL API Server without Docker. So please execute the following command in the terminal:
 
 ```bash
 vulcan package --output node
@@ -99,4 +99,45 @@ Congratulations! Now your VulcanSQL app is on the cloud and is ready to be share
 
 :::info
 If you need to clean up the resources on App Engine, you can [read the documentation here](https://cloud.google.com/appengine/docs/standard/python3/building-app/cleaning-up).
-:::
+:::
+
+## Step 4: (Optional) Deploy your VulcanSQL API Catalog Server
+
+If you need to deploy API Catalog Server, you should execute the following command in the terminal:
+
+```shell
+vulcan package -t catalog-server
+```
+
+:::caution
+The folder generated by the command is also called `dist`, so if you had executed the command of packaging
+API server, you should rename the `dist` folder generated previously to prevent from being overwritten.
+:::
+
+Now we need to do several things before deploying the app to App Engine:
+
+**1. Add `"config": {"port": 8080}` to `config.json`**
+
+Since App Engine accepts network traffic with the [port 8080](https://cloud.google.com/appengine/docs/flexible/custom-runtimes/build#listening_to_port_8080).
+
+**2. Change the filename of `index.js` to `server.js` and also in `package.json`**
+
+Since App Engine recognizes [`server.js`](https://cloud.google.com/appengine/docs/standard/nodejs/building-app/writing-web-service#running_the_server_locally) as the entry file.
+
+**3. Create a new file `app.yaml` and fill in the following content**
+
+```yaml
+runtime: nodejs
+env: flex
+runtime_config:
+    operating_system: "ubuntu22"
+    runtime_version: "18"
+env_variables:
+    VULCAN_SQL_HOST: [Your VulcanSQL API Server URL]
+```
+
+Finally, you execute the same Google Cloud CLI commands used in the step 3 in the terminal:
+
+```
+gcloud app deploy
+```

packages/doc/docs/deployment/gcp-cloud-run.mdx

@@ -25,9 +25,9 @@ Before you begin to use Cloud Run on GCP, you need to do several things:
 
 For more detailed instructions on how to setup the environment, you can [read more here](https://cloud.google.com/run/docs/quickstarts/build-and-deploy/deploy-nodejs-service#before-you-begin).
 
-## Step 2: Package your VulcanSQL project
+## Step 2: Package your VulcanSQL API Server
 
-In this guide, we'll deploy the Docker version of your VulcanSQL project. So please execute the following command in the terminal:
+In this guide, we'll deploy the Docker version of your VulcanSQL API Server. So please execute the following command in the terminal:
 
 ```bash
 vulcan package --output docker
@@ -104,4 +104,29 @@ Congratulations! Now your VulcanSQL app is on the cloud and is ready to be share
 
 :::info
 If you need to clean up the resources on Cloud Run, you can [read the documentation here](https://cloud.google.com/run/docs/quickstarts/build-and-deploy/deploy-nodejs-service#clean-up).
-:::
+:::
+
+## Step 4: (Optional) Deploy your VulcanSQL API Catalog Server
+
+If you need to deploy API Catalog Server, you should execute the following command in the terminal:
+
+```shell
+vulcan package -t catalog-server -o docker
+```
+
+:::caution
+The folder generated by the command is also called `dist`, so if you had executed the command of packaging
+API server, you should rename the `dist` folder generated previously to prevent from being overwritten.
+:::
+
+Then, you should modify `API_BASE_URL` to the URL of your VulcanSQL API Server you just deployed in Dockerfile:
+
+```dockerfile
+ENV API_BASE_URL [URL of VulcanSQL API Server]
+```
+
+Finally, you execute the same Google Cloud CLI commands used in the step 3 in the terminal, and change any configurations if you need:
+
+```
+gloud run deploy [YOUR_CLOUDRUN_SERVICE_NAME] --port=4200 --allow-unauthenticated
+```