Deployment strategy on fly.io
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
download all my books for free
- javascript handbook
- typescript handbook
- css handbook
- node.js handbook
- astro handbook
- html handbook
- next.js pages router handbook
- alpine.js handbook
- htmx handbook
- react handbook
- sql handbook
- git cheat sheet
- laravel handbook
- express handbook
- swift handbook
- go handbook
- php handbook
- python handbook
- cli handbook
- c handbook
subscribe to my newsletter to get them
Terms: by subscribing to the newsletter you agree the following terms and conditions and privacy policy. The aim of the newsletter is to keep you up to date about new tutorials, new book releases or courses organized by Flavio. If you wish to unsubscribe from the newsletter, you can click the unsubscribe link that's present at the bottom of each email, anytime. I will not communicate/spread/publish or otherwise give away your address. Your email address is the only personal information collected, and it's only collected for the primary purpose of keeping you informed through the newsletter. It's stored in a secure server based in the EU. You can contact Flavio by emailing flavio@flaviocopes.com. These terms and conditions are governed by the laws in force in Italy and you unconditionally submit to the jurisdiction of the courts of Italy.