Why it exists
Surge.sh's CLI expects an interactive login on first use, which doesn't work inside a CI job. This image wraps the CLI with the account credentials passed in as environment variables, so a static site build can deploy itself without a human in the loop.
What I learned
The smallest deployment tools are usually the ones worth containerizing first: less surface area, easy to get right once, and no reason to re-solve the same login/auth wiring in every project that needs it.
Status
Active. Still the deploy step for a few small static sites.