saturnism / buttonmasher

Hi there 👋

buttonmasher's Issues

Automate generating new containers and updating yaml files to deploy them

As it stands, the demo scripts all use the containers from gcr.io/hybrid-cloud-rocks, many of which embed a URL which the user can't change. It's not hugely useful without you building your own containers.

We should fix the default behavior to be to build the containers, push to your local project, and then automatically build the deployment yaml files with the local project name (which is already specified in Makefile.config.)

Frontend

• The domain name and QR code are hardcoded. This should be made configurable and a QR code autogenerated using a library.
• The URL the button calls should be auto-populated also. (This will depend on how we reconfigure Ingress).

Backend

• The backend works as-is, but needs to build v1 and v2 without human intervention. I have a PR in-flight for this.

Loader

• Doesn't require configuration and builds fine.

Aggregator

• Doesn't require configuration.

• Does not build, due to incorrect Kubernetes client library.

You can get it into your own project like so:

docker pull gcr.io/hybrid-cloud-rocks/buttonmasher-aggregator
docker tag gcr.io/hybrid-cloud-rocks/buttonmasher-aggregator gcr.io/kube-pw/buttonmasher-aggregator
docker push gcr.io/kube-pw/buttonmasher-aggregator

Other notes

• Release note: You need to have enabled Google Container Registry, and have an account with access to create buckets. The default service account on a GCE VM doesn't have the right scopes to do this.