Deployment strategy on fly.io
FULL-STACK WEB DEVELOPMENT BOOTCAMP
2024 COHORT SIGNUPS END TOMORROW
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.
Also see my Docker tutorials.
If you have multiple services, you communicate between them inside fly using the
.internal domain, like this:
You can also prepend the region to point to a specific one, for example:
Note that you also need the internal port, as specified in the app
fly.toml, for example
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