Skip to content

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.

Also see my Docker tutorials.

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

Are you intimidated by Git? Can’t figure out merge vs rebase? Are you afraid of screwing up something any time you have to do something in Git? Do you rely on ChatGPT or random people’s answer on StackOverflow to fix your problems? Your coworkers are tired of explaining Git to you all the time? Git is something we all need to use, but few of us really master it. I created this course to improve your Git (and GitHub) knowledge at a radical level. A course that helps you feel less frustrated with Git. Launching Summer 2024. Join the waiting list!

Here is how can I help you: