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

Operationalize master task #27

Open
1 of 12 tasks
mimoo opened this issue Feb 11, 2021 · 0 comments
Open
1 of 12 tasks

Operationalize master task #27

mimoo opened this issue Feb 11, 2021 · 0 comments
Assignees

Comments

@mimoo
Copy link
Contributor

mimoo commented Feb 11, 2021

To operationalize this we have to figure out a few things.

Where do we want this to live?

  • Association AWS
  • Novi AWS
  • or both? After all we care two use cases: novi stuff (custody, SLEDGE) and diem stuff (AOS, diem-core)

How do we want to deploy this?

  • easy ECS
  • easy EKS
  • terraform of ECS
  • terraform of EKS

(terraform pointer)

do we also want to move mongodb to a managed service like documentDB? (

IMO hat's more work for no real benefit

TODO

  • k8ify docker-compose with tool
  • clean dockerfiles (see this)
  • clean k8s files
  • dev -> prod-ify frontend (vuejs)
  • dev -> prod-ify backend (rocket)
  • dev -> prod-ify mongodb (user, creds, persistent volume)
  • helm/kustomize things
  • load balancer to serve both frontend and backend on same domain (this might require us to move all the requests to the API behind a /api route)
  • terraform apply that shit
  • create github action flow to create releases and push them to ECR easily (Golang has this amazing Goreleaser tool that creates releases for you every time you create a tag in Github, does the same exist for Rust?) (maybe https://docs.github.com/en/actions/guides/publishing-docker-images)
  • make sure errors are logged somewhere, and create alerts
  • figure access control
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants