Deployment Plan

[maozhenyu123]

Current Plan

1. Github CI gets triggered every time once there is new commit / merge on master / staging branch.
2. Github CI worker builds the frontend, and deploy it into classtranscribe.github.io/static/v-{hash}/*
3. Github CI worker updates the config.js, so that the index.html will use the latest version of frontend build

Downgrade

We manually change the config.js currentVersion variable to a previous version

Server Communication

Needs CORS header: https://classtranscribe.github.io
Cookie settings require SameSite policy, allowing classtranscribe.github.io to access

Pro

1. Easy to deploy
2. Costless
3. More reliable (frontend only)

Con

1. Cross-Site issue
2. Absolute path issue
3. Only one github page per org

Ideal Plan

1. Github CI gets triggered every time once there is new commit / merge on master / staging branch.
2. Github CI worker builds the frontend, and deploy it into Amazon S3 (with Cloudfront) etc.
3. Deploy version number/html into our backend server, import js bundle from the CDN

Pro

1. No cross site issue

Con

1. Reliability
2. Needs more work to deploy