Skip to content

[Issue]: Deploy Staging Environment using Azure #52

@soramicha

Description

@soramicha

Branch Name

feature/52-deploy-staging-azure

Task

We want to start deploying but in a staging environment (not production yet).

We are going to treat our database in Supabase that we currently have as our database for staging (not production). In the future, when we are ready, we will create a separate production database.

Steps:

  • Create a H4I account on Microsoft Azure - talk with Khoa regarding this part.
  • Go to Azure portal -> App Services -> Create; Set the name to "backend-staging"
  • Configure .env variables
  • Set up CD so it will automatically deploy our project to Azure whenever code is merged/pushed for the "develop" and "main" branch only (create a cd.yml in workflows folder)
  • If the Github Issue regarding the Notion data migration isn't done yet, then disregard this part. But if it's been complete, make sure that the Supabase is seeded with Notion data to imitate a realistic dataset.

Acceptance Criteria

  • Create a H4I account on Microsoft Azure
  • Create a cd.yml in workflows folder
  • Successfully deploy project on Azure with everything working
  • If Notion data has been migrated already, then ensure Supabase database has the same/similar data

Checklist

  • I have checked for duplicate issues.
  • I have assigned the issue to the correct project board.
  • I have tagged the issue properly.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

Labels

Type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions