Skip to main content

Documentation Index

Fetch the complete documentation index at: https://redop.useagents.site/docs/llms.txt

Use this file to discover all available pages before exploring further.

Use Fly.io when you want an always-on Docker-based deployment for Redop.

​
Before you start

This guide assumes:
  • your server uses the HTTP transport
  • the app binds 0.0.0.0
  • the app reads PORT
If you scaffolded with create-redop-app --transport http --deploy fly-io, the starter already generated:
  • Dockerfile
  • fly.toml
If your Redop app lives inside a monorepo, use the monorepo production image pattern from Deploy with Docker and adapt fly.toml to the same internal port.

​
Fly.io fit

ItemValue
Recommended transporthttp
App shapelong-running Bun service in Docker
Required env varsPORT is provided by Fly’s runtime and proxy setup
Deploy commandfly deploy
Generated filesDockerfile, fly.toml
Recommended foralways-on deployments and Docker-based workflows

​
Generated src/index.ts shape

import { Redop } from "@redopjs/redop";

new Redop({
  serverInfo: {
    name: "fly-redop",
    version: "0.1.0",
  },
})
  .tool("ping", {
    handler: () => ({ ok: true }),
  })
  .listen({
    port: Number(process.env.PORT ?? 3000),
    hostname: "0.0.0.0",
  });

​
Generated Dockerfile

FROM oven/bun:1

WORKDIR /app

COPY package.json bun.lock* ./
RUN bun install

COPY . .

EXPOSE 3000

CMD ["bun", "run", "src/index.ts"]
This generated Dockerfile is the single-project starter. For a monorepo app, switch to the monorepo production image from Deploy with Docker and keep the Fly internal port aligned with your Redop listener.

​
Generated fly.toml

app = "your-app-fly"

[http_service]
  internal_port = 3000
  force_https = true
  auto_start_machines = true
  auto_stop_machines = "stop"
  min_machines_running = 1

​
Deploy steps

  1. Install the Fly CLI and log in.
  2. From your project directory, run:
fly launch
  1. Review fly.toml and make sure the app’s internal port matches your Redop listener.
  2. Deploy:
fly deploy

​
Port and machine expectations

  • Keep the app listening on PORT with a default fallback like 3000.
  • Keep the listener on 0.0.0.0.
  • Fly proxies traffic to your internal app port from fly.toml.
  • If you need a separate health route, enable health: true or health: { path: "/health" }.

​
Verify the deployment

Replace the hostname with your Fly app hostname: 
curl -X POST https://your-app.fly.dev/mcp \
  -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":0,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"fly-check","version":"1.0.0"}}}'
What success looks like:
  • the app is reachable over HTTPS
  • /mcp returns a valid JSON-RPC initialize result
  • your Fly machine stays up for MCP requests instead of behaving like a short-lived function

​
Next