Switch to GitHub actions to deploy

[dustinwalker]

Proposal is to use Github actions for build and deploy process.

Pros:

• Decouple nodejs from the server, as it won't be building it. We can use different build processes on same server.
• Offload process resources from production server to Github's Docker
• Enable things like linting on building
• Email notifications of issues

Cons:

• Difficult branch switching (idea next comment)
• Reliant on GitHub queue to deploy
• Limited to 2000 minutes of free build time

Requirements

• Strategy to handle staging and production
• Scope version tags to master/main only
• Possibly look into symlinking directories (not sure this is needed considering how fast rsync is)
• Update toolkit to handle populating sample data
• Add documentation

[dustinwalker]

My idea to handle triggering the deployment around tags. I don't have it working perfectly yet (mostly around ignore -rc and -beta tags on production) but the idea is:

• <vx.x.x> would deploy to production
• <any-other-tag> deploys to staging
• <any-tag>-beta or <any-tag>-rc would lint the project and email any code issues in src

[dustinwalker]

If you want to see the yaml that controls this: https://github.com/astuteo-llc/build-config/tree/feature/5/reference/.github/workflows

[dustinwalker]

@astuteo would you be up for testing this out on the Biotech project?

[astuteo]

Sure, it's just a giant sandbox for everything at this point.