What I built

A simple proof-of-concept sidecar proxy¹ that injects Web Monetization meta tags into HTML responses from the backend application. Offloading this responsibility to a sidecar is valuable for several reasons:

1. It allows applications to benefit from Web Monetization without having to change the code of the application itself. Useful for cases where there are many applications being deployed or when the application is not modifiable (e.g. commercial off the shelf software).
2. Platform operators could automatically deploy these sidecars across their entire cluster without application developer intervention.

While the proxy I built for this Hackathon is far from production ready, I hope that this proof-of-concept can inspire further work. One idea might be writing a WASM filter for Envoy proxies that does this work.

Included with the code is an example Kubernetes Deployment that showcases how the proxy can easily be added to an existing Pod as a sidecar container.

¹ - What is a sidecar proxy? It is a sidecar container that runs a proxy sitting in front of your "main" application container. Sidecars are frequently used by service meshes to enable features like intelligent load balancing, rate-limiting, certificate / TLS management, and more. Envoy is a commonly used sidecar proxy.

Submission Category:

Foundational Technology

Demo

Demo: https://monetization-proxy.k8s.downey.dev/

I've deployed a sample Ghost blog running with the monetization proxy sidecar to a small development Kubernetes cluster running on Digital Ocean². The site can be accessed at here. Additionally, you can view the Kubernetes deployment configuration here.

² - This cluster costs money so I will tear it down in a few weeks.

Link to Code

The proxy is available as a Docker image here.

How I built it

The proxy is built using Go and uses an httputil.NewSingleHostReverseProxy to do a lot of the heavy lifting around proxying. A response modifying function is applied to each response from the backend and does the following:

1. Checks to see if the response Content-Type is HTML. If it is not, we leave the response alone since we don't want to inject meta tags into Javascript or CSS responses!
2. If it is HTML, we parse the DOM and inject the Web Monetization meta tag into the document head.

For unit testing I used https://github.com/sclevine/spec which provided some lightweight BDD goodies to Go's built-in testing library. It was my first time using it (I traditionally have used Ginkgo and Gomega) and I found it to be easy to work with.

For building the OCI images I used the Go Cloud Native Buildpack and kbld to streamline the build/push/deploy to Kubernetes flow. More details on that are in the project README.

To deploy the demo I set up a Kubernetes cluster on Digital Ocean. I used NGINX as my Ingress controller and set up automatic provisioning of TLS certificates using Cert-Manager and LetsEncrypt.

Additional Resources/Info

This was a fun little project for me. I got to write some Go, set up a a new K8s cluster, and play around with some new libraries / tools.

One thought I had while working on this though was "I sure wish there was just a Web Monetization HTTP header" instead of having to rely on meta tags. This would have let me just use an off-the-shelf sidecar proxy like Envoy which supports header manipulation and would have opened it up to support non-HTML applications.