I currently have a service running on a VPS; it’s a simple Docker Compose stack consisting of a Traefik container to handle SSL termination and a custom Docker image that contains my Go backend. I’m interested in fly.io for the autostop/autostart capabilities so that I could scale to 0 since the service will be used infrequently. Is there an easy way to make this work on fly.io? I’m not sure how to approach the platform for this use case.
Thanks!
Hi… The Fly Proxy handles SSL termination by default, so if that’s the only reason you needed Traefik on the VPS, then you can probably dispense with that container here—and just follow the Go instructions.
(illustration by Annie Ruygt)
Having said that, there is initial Docker Compose compatibility now, if it turns out that you also need path rewriting, or similar…
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
