search

ContactTracing-app / Graphql-api

GraphQL API layer on top of neo4j for Contact Tracing: notifying friends & family against COVID-19
https://contacttracing.app/
ISC License
5 stars 5 forks source link

Set-up Backend CI #6

Open mmmoli opened 4 years ago

gcristofol commented 4 years ago

What's the endgame here? Move away from cloudbuild? Using github actions instead?

mmmoli commented 4 years ago

@gcristofol thanks for asking 🙏🏻

I'm not going to answer very well.

If that makes sense, yeah! Our api runs on Google Cloud Run right now. Usage is low enough that we're well within the limits of the discount so cost is £0.

It's fine, and it works, but I'm worried it's going to get pricey.

Plus digitialocean gave us free credits so I feel guilt for not using them.

One idea I've had: we have a Firebase-Functions project to do some operations behind the scenes, I was thinking of running our own lambda provider; again just to save costs.

What would you recommend?

gcristofol commented 4 years ago

@mmmoli I can have a go at the k8s manifests first (issue #2) add that to the repo and then have a go at github actions. Changing from do to another managed kuberentes should be an easy change at that point

mmmoli commented 4 years ago

@gcristofol that would be 👌😎💯

gcristofol commented 4 years ago

I created a workflow on my fork of this repo: dockerworkflow

Once the k8s resources are merged, this can be added to trigger docker builds and pushes on master