3 ms·
Show HN: Heroku/Fly.io-like app deployments to Cloudflare Containers
The Cloudflare ecosystem is great. I love deploying apps to Workers, but not all applications can be ported to serverless architecture.
Cloudflare Containers have been around for a while (still in beta though) to address that. They are using Firecracker VMs under the hood (https://firecracker-microvm.github.io/ https://firecracker-microvm.github.io/) and allow you to deploy any Docker image across their infrastructure.
But for somebody who just wants to take their Docker image and deploy, going through the whole Wrangler setup, writing a Worker script, dealing with Durable Objects may be discouraging for quick experimentation.
I built a simple Node.js CLI that implements Heroku/Fly.io developer experience on top of Cloudflare Containers.
1. Open directory with Dockerfile
2. Auth with Cloudflare API token
3. Deploy
- it will create a routing/loadbalancing worker
- add Durable Objects and Container bindings
- and return live app url within couple of minutes
You can then play with scaling it across regions and instances:
```
flarepilot scale myapp -r eeur,weur -i 1
flarepilot scale myapp -r eeur -i 4
```
It is a very basic proof-of-concept using locationHints, not ready for production.
Just experimenting for fun.
- maxxmini 9mo ago[flagged]
- michaloo 9mo agoThanks! Based on my impressions CF Containers are slower to boot but have lower latency later. I moved some test apps from DigitalOcean App and I saw 10-20% improvements in loading time (which is different what you asked since DigitalOcean is probably more k8s than firecracker, but just to share my experience).