Skip to content

v1.2.5-alpha.1 #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 28, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pages/directories/server.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Knowing that there are two _(2) points of data entry_ to anticipate and the _nat
### /api

- Contains the `index.js` file that converts the stand-alone Express app into a single serverless function format recognized by Vercel.
- This option only becomes available if deployment to Vercel is activated.
- This option only becomes available if [deployment to Vercel](/articles/deployment-vercel) is activated.

## Express server (Folder)

Expand Down
8 changes: 4 additions & 4 deletions docs/pages/post-installation/acap-rcmas-api.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,19 +4,19 @@ import { Callout } from 'nextra/components'

The **ACAP-RCMAS REST APIs**, aiming to share ACAP's internal PAGASA weather forecast data in a structured, organized format and secure manner to collaborators, are a new addition to ACAP's REST APIs. Merging its feature updates from the forked development repository and environment into the official ACAP Bicol aims to:

- Unify **datadata sources** and **processes**, merging specific updates from the ACAP Bicol's **mirror environment** to the **official** ACAP Bicol environment.
- Unify **data sources** and **processes**, merging specific updates from the ACAP Bicol's **mirror environment** to the **official** ACAP Bicol environment.
- Make the APIs readily available for other regions should the DA request its activation and availability.

These APIs, accessible in the `/api/weatherforecast` and `/api/weatherforecast/archives` REST API endpoints, provide GET query methods for retrieving seasonal, 10-day, and severe cyclone weather forecasts. Furthermore, its inclusion in ACAP allowed the archiving of historical weather forecast data, also available by query in these API endpoints.

These APIs are in their prototype stage, currently for use only by the **Bicol** region for sharing structured and organized weather forecast data with IRRI as part of their collaboration project.
These APIs are in their prototype stage, currently intended for use only by the **Bicol** region for sharing structured and organized weather forecast data with IRRI as part of their collaboration project.

> Activation of the ACAP-RCMAS APIs is made into an optional feature for ACAP 2.0 that can be triggered by supplying certain backend environment variables and GitHub Secrets/Variables to ensure smooth integration with the standardized ACAP 1.0 deployments for other regions, which does not yet require these APIs.

<Callout type="info" emoji="ℹ️">
**Regions** outside Bicol _are encouraged to **prevent** these APIs and their respective archiving and deletion functions from running and being accessible until further notice by the DA since **ACAP (for other regions) does not yet endorse activating the ACAP-RCMAS REST APIs.**_
**Regions** outside Bicol _are encouraged to **prevent** these APIs and their respective archiving and deletion functions from running and being accessible until further notice by the DA._

Other regions can also start activating and using it earlier.
**While ACAP does not yet endorse activating the ACAP-RCMAS REST APIs for other regions**, other regions can also start activating and using it earlier.
</Callout>

<Callout>
Expand Down