[26.3] PI Objective 3: Deployment Strategy for MMGIS

[BhattaraiSijan]

Motivation:

Since the deadline for disasters tool and air4us tool is fast approaching, the deployment strategy should be figured out sooner rather than later

Description:

• Currently, the MMGIS app is tightly coupled with a backend service that allows user authentication for tool building, sharing draft tools, realtime sync of drawn features, geodatasets etc. This is great for the tool building functionality, but for a production site, all we want is a static webapp that’s deployed via s3 or amplify for simplicity and cost effectiveness.
• This will need an ADR to figure out the splitting of MMGIS into internal tool building deployment + public static website and deployment strategy for both.

Tasks include:

• Decoupling of frontend from backend
• Test deployment of an MMGIS built viz tool via aws
• (stretch/low priority) Test deployment of an MMGIS builder app via aws

Acceptance Criteria:

• A decision is made on how to deploy MMGIS configure/tool builder UI
• A decision is made on how to decouple and deploy the frontend only dashboard
• test deployment of an MMGIS built tool