Eurobase
Log InSign Up

Move from Fly.io to Eurobase

This guide moves a Fly.io app to Eurobase: the start command, secrets, port, database and domain. Eurobase builds from your GitHub repository and runs the app as a container that scales to zero.

What moves where

On Fly.ioOn Eurobase
App deployed with fly deployProject from a GitHub repository
Dockerfile or buildpack builderPaketo buildpacks; Dockerfiles aren’t used
[http_service] internal_portThe port
[[http_service.checks]] pathThe health path
[env] and Fly secretsSecrets
Other [processes] groups and release_commandNot available
Volumes in [mounts]Not available
Fly Managed PostgresMove to an EU provider

Step 1: Export your secrets

Copy the [env] values from fly.toml. fly secrets list shows only the names of your secrets; to read their values, print the environment of a running Machine:

fly ssh console -a <your-app> -C "printenv"

Skip the variables Fly sets itself, such as those starting with FLY_.

Step 2: Create the project

  1. Push your code to GitHub if it isn't there yet: Eurobase deploys from a GitHub repository.
  2. Create an account, connect GitHub and install the Eurobase GitHub App on the repository.
  3. In Projects, select New project, choose the repository and the service's root directory, then check the detected start command.
  4. Set Port and Health path as described in step 3, then select Save and Deploy.

Eurobase builds Node.js, Python, Go, Java, Ruby, PHP and .NET apps; apps in other languages can't be built. A single web: line in a Procfile becomes the start command. Node.js apps need npm or Yarn 1: pnpm and Bun projects are refused before the build.

Next.js, Astro, SvelteKit, Nuxt and TanStack Start apps run on V8 isolates instead of a container, with no port to set. For those, follow Move from Vercel from step 3.

Step 3: Check the port and health path

Fly sends traffic to internal_port in fly.toml, 8080 by default.

On Eurobase, set Port to the port your app listens on (3000 unless you change it); the same value is in PORT. Listen on 0.0.0.0. A deployment goes live only after your health path answers GET with 2xx or 3xx; otherwise the previous deployment keeps serving.

Step 4: Add your secrets

In the Eurobase project, open Secrets, add each value and choose the resources that receive it. Every value is stored encrypted. Secrets reach your code when it runs, not during the build, so values your build needs must come from your repository.

A secret reaches your app with its next deployment, so redeploy once your secrets are in place.

Step 5: Your database

Eurobase doesn't offer a managed database yet. Your container can keep using your current database, Redis or Valkey with its native driver, through its public address. Fly Managed Postgres runs inside your Fly private network, so plan to move its data before the switch.

To move the data to Europe, dump and restore it into an EU provider, such as Supabase in an EU region, with your app in maintenance mode during the copy. Then update the connection string in Secrets and redeploy.

Step 6: Move your domain

  1. Before the move, lower the TTL of your domain's DNS records so the switch spreads quickly.
  2. In Eurobase, open Domains in the sidebar, select Connect domain, enter your domain and choose the project. Only the workspace owner can connect domains.
  3. Add the DNS records Eurobase shows at your DNS provider, then wait until Eurobase marks the domain ready.
  4. Once your domain serves the Eurobase app, remove it from the old platform.

What doesn’t carry over

  • Process groups other than the web process, such as workers: Eurobase runs one web service per project.
  • A release_command, such as database migrations: run it yourself before you push.
  • Machines you start and stop through the Machines API: Eurobase starts and stops instances with traffic.
  • Persistent disks: containers scale to zero when idle, so keep files in a database or in your project's Storage, not on the container's disk.
  • Private networking: your app reaches other services over their public addresses.
  • Preview deployments: a project deploys one branch.
  • Instance counts and sizes: your plan sets them, and the first request after an idle period waits for your app to start. See Plans and limits.

After the move