Deployment strategy on fly.io
New Course Coming Soon:
Get Really Good at Git
Found this interesting.
I was used to similar services that used a single file named docker-compose.yaml
to set up multiple services.
On fly, each service in your app lives on its dedicated service, deployed independently, each with its own Dockerfile.
If you have multiple services, you communicate between them inside fly using the .internal
domain, like this: myappname.internal
You can also prepend the region to point to a specific one, for example:
cdg.my-app.internal
Note that you also need the internal port, as specified in the app fly.toml
, for example cdg.my-app.internal:8080
I wasn’t able to set this up with my PocketBase instance yet, but that’s the goal.
Related issues https://github.com/pocketbase/js-sdk/issues/21
Here is how can I help you:
- COURSES where I teach everything I know
- THE VALLEY OF CODE your web development manual
- BOOTCAMP 2024 cohort in progress, next edition in 2025
- BOOKS 16 coding ebooks you can download for free on JS Python C PHP and lots more
- SOLO LAB everything I know about running a lifestyle business as a solopreneur
- Interesting links collection
- Follow me on X