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
→ I wrote 17 books to help you become a better developer:
- C Handbook
- Command Line Handbook
- CSS Handbook
- Express Handbook
- Git Cheat Sheet
- Go Handbook
- HTML Handbook
- JS Handbook
- Laravel Handbook
- Next.js Handbook
- Node.js Handbook
- PHP Handbook
- Python Handbook
- React Handbook
- SQL Handbook
- Svelte Handbook
- Swift Handbook
Also, JOIN MY CODING BOOTCAMP, an amazing cohort course that will be a huge step up in your coding career - covering React, Next.js - next edition February 2025