Installation and Setup

Introduction

This series of tutorials describes how to run ACAP-Bicol (ACAP version 2.0) on localhost, using values for a new Region, using the initial ACAP 2.0 release version v10.1.0-alpha.1, dev branch @commit c92235b.

Fork the repository to receive the latest updates and bug fixes. Configure the following components to run ACAP for your PC or laptop for localhost development.

To make the most of these tutorials, please create Firebase projects first as instructed from the 03 Create Firebase Projects (opens in a new tab) video tutorial before proceeding.

💡

acap-v2 has updated source codes at Release tag v10.1.0-alpha.10 dev branch @commit 95a97cd.

A. Firebase Initialization B. Server Setup C. Client Setup D. Integration E. Accounts F. Conclusion

Post-Installation

After installing ACAP, additional setup is required, including configuring the web map on the Home Page, updating static PDF content, and replacing the OpenGraph thumbnails.

For detailed instructions on these steps, refer to the Post-Installation section after completing the Installation process.

Repository Syncing Options

If you are working on a forked repository behind several updates from the parent acap-v2 repository, you can get the latest updates or bug fixes using any of the options:

"Sync" your forked repository's dev branch to the parent repository's dev branch.
⚠️
Take care not to "discard" your commits.
Create a Pull Request (PR) from the "parent" repository's (acap-v2) - dev branch to your "forked" repository's dev branch, then merge/resolve conflicts.
Pick only the target updates/fixes, then commit them to your fork.

ℹ️

Project Maintainers occasionally update the parent repository acap-v2 for maintenance, bug fixes, and minor/optional updates. Sometimes, massive new feature updates.

Of the three (3) repository syncing options mentioned, doing the first or second options ensures up-to-date sync with the latest updates and bug fixes.

💡

All updates and fixes should be from the (parent) acap-v2 repository's (default) dev branch. Updates to the acap-v2 dev branch expect to have been tested and ensured compatibility by the main ACAP code Maintainer(s) before committing new updates and fixes to the dev branch.

Questions and Inquiries

Concerns, questions, and inquiries with ACAP go through the mode of communication channel elected within ACAP (the ACAP FB Group Messenger).

This communication channel is reserved only for the "active" and "official" ACAP members group.
Alternatively, developers may create tickets (GitHub Issues) within the (parent) acap-v2 repository (opens in a new tab) to describe their concerns in more detail. This page also contains code-related information about past inquiries and bug fixes that may be useful to other regions.

The main ACAP code Maintainers ("active" and "inactive") may respond to these tickets within their available time.

Requirements Firebase Initialization