https://<app>.getfloo.app, with server-rendered routes, managed Postgres, signed-in users, and your own domain. Remix v2 apps follow the same steps after the upgrade to React Router.
New to floo? Start with the Quickstart.
What your agent controls
floo builds theDockerfile in your repository. Add one that specifies the runtime for your app:
- The base image and the exact Node version.
- System packages, such as
ffmpegor Chromium for headless browsing, each oneapt-get installline. - The build steps and the start command, including a custom Express server if you need one.
- More services from the same repository, such as a background worker or a cron job.
floo.app.toml. Store secrets outside git.
1. Add a Dockerfile
This uses the project layout fromnpx create-react-router@latest, where npm run build runs react-router build and writes build/client and build/server. @react-router/serve runs the result. The starter ships its own Dockerfile and .dockerignore; replace the Dockerfile with this one, which orders layers for faster pushes:
Dockerfile
react-router-serve reads PORT and listens on every interface. Keep @react-router/serve in dependencies, which the starter template does, so npm prune leaves it in the image.
2. Initialize the floo config
Install the CLI and sign in:curl -fsSL https://getfloo.com/install.sh | bash, then floo auth login. An agent can run the same journey over the HTTP API instead, starting from getfloo.com/agents.md.
floo.app.toml
migrate_command under [services.web] to your migration tool, such as "npx drizzle-kit migrate". Keep that tool in dependencies so npm prune leaves it in the image, and copy its config and migration files into the final stage. It runs as a one-off job with the new image before traffic moves to it. A failed migration stops the deploy. Use expand-then-contract migrations to keep the schema compatible with both old and new code.
3. Connect the repo and deploy
floo builds from your GitHub repository, not local files, so commit first.floo deploy pushes the commit and waits until the dev URL is live. The first time, it stops with one link if the floo GitHub App can’t read the repository yet: a human opens it and installs the App on the account that owns the repository, then you run floo deploy again. See Give floo access to your GitHub repository.
floo deploy --hosted has floo host the repository. See Deploy without GitHub.
When it’s done:
Your React Router app is live at
https://my-react-router-app.getfloo.app.Every git push origin main ships to dev.4. Add a Postgres database
floo.app.toml
MANAGED_CREDS_TO_WEB because the web service receives the database credentials. That is expected when the web service queries the database.
DATABASE_URL is injected at runtime. The .server.ts suffix keeps the module out of the browser bundle:
app/db.server.ts
app/routes/home.tsx
postgres connects on the first query and reads the TLS settings in the URL. Dev and prod each get a separate Postgres database and credentials, with no shared state.
5. Add per-user auth
Setaccess_mode = "accounts" and floo handles sign-in:
floo.app.toml
- Redirects unauthenticated requests to a hosted login page.
- Validates the session cookie on every request.
- Injects identity headers into every request that reaches your React Router server.
app/user.server.ts
app/routes/dashboard.tsx
app/routes.ts with route("dashboard", "routes/dashboard.tsx"). Locally, run floo dev --fixture-user (see section 7) or send the headers yourself with curl -H 'X-Floo-User-Email: you@example.com' .... Access modes and identity headers in full: App sign-in.
6. Add a custom domain
Declare the domain infloo.app.toml:
owner/repo with your GitHub repository. For a floo-hosted project, see Environments.
show prints, then watch
activation:
react-router-serve serves every host, so it needs no extra config. DNS setup and troubleshooting: Custom domains.
7. Local development with dev credentials
dev_command locally with DATABASE_URL and readable env vars from the app’s dev environment: a real connection to your dev Postgres, with no credentials in your shell history. Write-only secrets are withheld; supply separate local values when needed. Prod credentials never reach a local session.
The database exists after the first deploy that declares [managed.default]. Before that deploy, floo dev starts without DATABASE_URL.
To test signed-in flows, add --fixture-user:
floo dev then puts a proxy in front of each accounts-mode service that injects the same X-Floo-User-* headers floo’s gateway adds in production. The output table shows the raw service URL and the auth-proxied URL; use the auth-proxied one for any path that reads identity headers.
Common gotchas
/healthzis reserved. floo’s edge intercepts that exact path. Use/healthor/livez.--host 127.0.0.1indev_command. On macOS the dev server listens on::1by default, and thefloo dev --fixture-userproxy reaches it at127.0.0.1. Without the flag, proxied requests fail with an empty reply.ssr: falsebuilds a static app. With server rendering off inreact-router.config.ts, there is no server to read identity headers or query the database. Keep the defaultssr: true.- Client values at build time. floo passes
VITE_*variables to the build as build args. Thread them through the build stage asARGplusENVbeforenpm run build. See Build-time variables. - Keep database and secret code in
.server.tsmodules. A module without the suffix can end up in the browser bundle.
Next steps
App sign-in
Identity headers, access policies, and access modes in detail.
Environment variables
Secrets, build-time variables, and per-service values.
Dockerfiles
Layer order for fast pushes and recommended multi-stage builds.
Production environments
Dev vs prod, promotion, env overrides.