Skip to main content
Fly.io deploys Docker containers as apps close to your users. This guide uses Fly Launch to configure and deploy ParadeDB Community with a persistent volume.

​
Prerequisites

  1. A Fly.io account
  2. The Fly.io CLI (flyctl) installed and authenticated with fly auth login

​
Launching the App

From an empty directory, run fly launch and point it at the ParadeDB Docker image. The --no-deploy flag lets you edit the generated fly.toml before the first deploy so you can add the persistent volume and secrets:
The command prompts for an app name and a primary region, then writes a fly.toml in the current directory. See Docker Hub for available tags.

​
Creating a Persistent Volume

Create a Fly.io volume in the same region as the app so data survives restarts and redeploys:
Replace <REGION> with the region you chose during fly launch.

​
Setting the Postgres Password

Store POSTGRES_PASSWORD as a Fly.io secret to keep it out of your configuration file.

​
Deploying ParadeDB

Add the database settings and persistent volume mount to your fly.toml:
Then deploy the app:
Fly.io starts ParadeDB with the configured database settings and persistent storage.

​
Connecting to ParadeDB

​
From Your Local Machine

Open a local connection to ParadeDB through Fly.io’s proxy:
Keep the proxy running and connect with psql from another terminal:

​
Public Connections

To make ParadeDB accessible over the internet, configure a TCP service on port 5432 in fly.toml and allocate a dedicated IPv4 address:
Use a strong password for public connections. See Fly.io’s networking documentation for service configuration details.