Skip to content

Commit 8d32bfb

Browse files
Merge pull request #71 from acaptutorials/dev
v1.2.5
2 parents 451f33b + 613a3db commit 8d32bfb

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/pages/articles/deployment-vercel.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,12 @@ import { Callout, Steps } from 'nextra/components'
22

33
# Deployment to Vercel
44

5-
ACAP Bicol started deploying its Node backend to Vercel along with the official Render deployment starting in its 2.0 version, aiming to achieve faster API response times than its (standard-pricing) Render-deployed APIs that experience 30 secs - 1 minute cold starts specifically for its [ACAP-RMCAS APIs](/post-installation/acap-rcmas-api).
5+
ACAP Bicol started deploying its Node backend to Vercel along with the official Render deployment starting in its [2.0](/changelog#version-2-acap-20) version, aiming to achieve faster API response times than its (standard-pricing) Render-deployed APIs that experience 30 secs - 1 minute cold starts specifically for its [ACAP-RMCAS APIs](/post-installation/acap-rcmas-api).
66

77
<Callout>
8-
**ACAP does not officially endorse deployment to Vercel** nor **activation of the ACAP-RMCAS APIs for <u>other regions</u>**. This deployment and new API endpoints (also accessible in the official Render deployment) are only for the prototype development purposes of sharing <u>ACAP Bicol's</u> internal PAGASA-sourced weather forecast data with collaborators, which needed to start using **unified data sources** and **processes** from July 2024.
8+
**ACAP does not officially endorse deployment to Vercel** nor **activation of the ACAP-RMCAS APIs for <u>other regions</u>**. Therefore, no step-by-step video guides demonstrate its initialization and usage, unlike the supported Render <sup>[[1]](https://youtu.be/IyGmWzoFPZE)</sup> <sup>[[2]](https://youtu.be/_Ese9uCXizE)</sup> deployment.
9+
10+
The Vercel deployment and new API endpoints (also accessible in the official Render deployment, if activated) are only for the prototype development purposes of sharing <u>ACAP Bicol's</u> internal PAGASA-sourced weather forecast data with collaborators, which needed to start using **unified data sources** and **processes** from July 2024, with an option to be activated by other regions upon request by the DA.
911

1012
All ACAP Node REST APIs (except for PDF bulletin creation) are supported in its **Vercel** deployment.
1113
</Callout>
@@ -95,7 +97,7 @@ Repeat the following steps to initialize an ACAP server app for deployment to th
9597
```
9698
</Callout>
9799

98-
4. Confirm the creation of an empty Node app with the **project name** from the prompt in the Vercel project's dashboard.
100+
4. Confirm the creation of an empty Vercel app with the **project name** from the prompt in the Vercel account's projects dashboard.
99101

100102
5. Go to **(Vercel Project)** -> **Settings** -> **Environment Variables**. Set the environment variables similar to the **"DEVELOPMENT"** Render Environment Variables.
101103

@@ -190,7 +192,7 @@ These steps will initialize an ACAP server app for deployment to the **"PRODUCTI
190192
```
191193
</Callout>
192194

193-
6. Confirm the creation of an empty Node app with the "PRODUCTION" project name created by the prompt in the Vercel project's dashboard.
195+
6. Confirm the creation of an empty Vercel app with the "PRODUCTION" project name created by the prompt in the Vercel account's projects dashboard.
194196

195197
7. Go to the PRODUCTION" **(Vercel Project)** -> **Settings** -> **Environment Variables**. Set the environment variables similar to the "PRODUCTION" Render Environment Variables.
196198

0 commit comments

Comments
 (0)