This seems like a trivial thing to add. If I wanted to use a domain specific configuration file then that's always an option, later.
This seems like a trivial thing to add. If I wanted to use a domain specific configuration file then that's always an option, later.
Fly devs have confirmed this is in the works, think macaroons.
The only defense here is that Fly isn't the only party being incredibly sloppy with their API keys. Cloudflare is just as bad.
Doesn't that force you to use your hosting provider as your CI provider?
I've always avoided the automatic "deploy on git push" solutions because I want to keep my CI provider uncoupled from my hosting provider. That way, I can switch hosts without having to rewrite all my CI code.
About 1/3 of my deployments are just static sites, and the rest all fit into a single Docker container, so integrating Compose would be a big increase in complexity.
That being said, you can use Watchtower without Compose. It's enough to run
docker run -d -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower