Hey HN,
I have way too many sideprojects so docker images have been eating up most of my RAM, but besides "deploy them" there isn't much I can do during development to cut it down.
So I build Bridgeflare - a drop-in docker replacement that serves the containers on Cloudflare then tunnels them back to you as localhost.
It basically a small daemon that uses the Docker API, so you can just keep using normal docker CLI commands and bridgeflare will do the work underneath:
- Build your image
- Deploy to CF containers
- Setup tunneling across services
- Tunnel them back safely to your machine so you see them as `localhost`
- Small MacOS menu bar to monitor the running containers for ease of use
In a way, it's like the reverse of CF's recently released quick tunnels.
As always, it is early and there are some limits:
- Images need to be amd64 based (CF containers limits)
So I build Bridgeflare - a drop-in docker replacement that serves the containers on Cloudflare then tunnels them back to you as localhost.
It basically a small daemon that uses the Docker API, so you can just keep using normal docker CLI commands and bridgeflare will do the work underneath:
- Build your image
- Deploy to CF containers
- Setup tunneling across services
- Tunnel them back safely to your machine so you see them as `localhost`
- Small MacOS menu bar to monitor the running containers for ease of use
In a way, it's like the reverse of CF's recently released quick tunnels.
As always, it is early and there are some limits:
- Images need to be amd64 based (CF containers limits)
- No docker exec
- No post-lifecycle persistence