Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document/outline the tech stack #61

Open
abettermap opened this issue May 24, 2020 · 0 comments
Open

Document/outline the tech stack #61

abettermap opened this issue May 24, 2020 · 0 comments
Labels
effort: 3 (med) Moderate amount of work focus: documentation Documentation tasks such as Markdown, inline code comments, wiki, etc. priority: 2 (low) Should be completed after med-priority relates: org repos Requires changes to or from other repos within this GH org. type: enhancement New feature or functionality to introduce.

Comments

@abettermap
Copy link
Contributor

abettermap commented May 24, 2020

Description

Lots of moving parts, good to know how they all fit together (esp. for new contributors) in a README or Wiki.

Front end

  • React, creat-react-app
  • Material UI
  • Basically just look at package.json
  • PR's should generate deploys automatically. Amplify not working, switch to GH Actions?

Back end

(internal/core group has dev and prod keys for many of these)

  • AWS Amplify for deploys and builds (connected to GitHub repo)
  • AWS Lambda with Flask for creating API endpoints (/self-report, /countries, etc.). Documentation via Swagger (???) started but need to learn the process now that Gabe is gone.
  • AWS DynamoDB to store user submissions
  • AWS DynamoDB to store COVID data (just countries now), scraped from JHU on a (???) basis
  • AWS Route53 for domains
  • The API in AWS was set up using Zappa (Python scaffold thing for AWS)
  • Google Firebase to handle user auth

Accounts and platforms

  • Jira for proj mgmt migrating away from this in favor of GH Issues
  • GitHub organization (Jason set up), no GH user created. Connected to Jira and AWS.
  • Gmail acct
  • MapBox (no billing info entered, 200k tiles views free per month)
  • FB developers (to allow auth via FB)

Related items

Jira CSR-176

Jira CSR-177: Explain the front-end PR auto-deploy process:

Anyone who contributes to front end repo should know:

  • Their PR's trigger deploys for review.
  • How to find the link.

Resolution

Decide on README vs Wiki then polish it up.

@abettermap abettermap added focus: documentation Documentation tasks such as Markdown, inline code comments, wiki, etc. type: enhancement New feature or functionality to introduce. effort: 3 (med) Moderate amount of work priority: 2 (low) Should be completed after med-priority relates: org repos Requires changes to or from other repos within this GH org. labels May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: 3 (med) Moderate amount of work focus: documentation Documentation tasks such as Markdown, inline code comments, wiki, etc. priority: 2 (low) Should be completed after med-priority relates: org repos Requires changes to or from other repos within this GH org. type: enhancement New feature or functionality to introduce.
Projects
None yet
Development

No branches or pull requests

1 participant