mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-09-06 08:18:58 +00:00
b96647314c
Reframe the deployment docs around the actual product story: Fabro runs as a server, and the only deployment question is where that server runs (laptop vs self-hosted Docker). Drop the Render, Fly.io, and DigitalOcean guides and their config files; keep Railway as the managed shortcut. - New: administration/deployment.mdx (overview, two-mode framing) - New: administration/self-host-docker.mdx (compose-first how-to) - Move: administration/deploy-server.mdx -> reference/server-operations.mdx (it was operational reference, not deploy guidance) - Delete: deploy-render.mdx, deploy-fly-io.mdx, deploy-digital-ocean.mdx - Delete: render.yaml, fly.toml, railway.toml, Dockerfile.deploy - docker-compose.yaml: load .env if present so users can drive the stack from a single env file end-to-end - Update internal links and the docs-test that pinned the old path
42 lines
2.2 KiB
Text
42 lines
2.2 KiB
Text
---
|
|
title: "Deployment"
|
|
description: "Choose where the Fabro server runs: on your laptop or self-hosted on a server"
|
|
---
|
|
|
|
<Warning>
|
|
The server interface is in private early access. Contact [bryan@qlty.sh](mailto:bryan@qlty.sh) if you're interested in trying it.
|
|
</Warning>
|
|
|
|
Fabro runs as a server. The CLI authenticates and communicates with that server, whether the server is running on your laptop or on a remote host. Choose where the server runs based on how you use Fabro.
|
|
|
|
## Two deployment modes
|
|
|
|
| | Local | Self-hosted |
|
|
|---|---|---|
|
|
| **Where the server runs** | Your laptop | A host you operate (Docker container) |
|
|
| **How to start it** | `fabro server start` | `docker compose up -d` |
|
|
| **Best for** | Solo use, getting started, learning | Teams, production, 24/7 workflows |
|
|
| **Trade-off** | Workflows pause when your laptop sleeps or shuts off | You operate the host |
|
|
|
|
Both modes use the same image, the same workflow engine, and the same CLI. The only difference is where the server process lives.
|
|
|
|
## Local
|
|
|
|
Run `fabro server start` on your machine. State persists under `~/.fabro/`. The CLI talks to it over a Unix socket by default. This is the right mode for solo use and getting started — no deployment required.
|
|
|
|
When your laptop sleeps or shuts off, in-flight workflows pause until the laptop wakes again. For workflows that need to run 24/7 or for teams sharing a single instance, self-host.
|
|
|
|
See [Server Operations](/reference/server-operations) for starting the server, the install wizard, authentication, and pointing the CLI at it.
|
|
|
|
## Self-hosted
|
|
|
|
For team use, production workflows, or running 24/7, self-host the server as a Docker container. The recommended approach is `docker compose` for a single host, or any cloud container service (ECS, Cloud Run, Kubernetes) using the same image with the same requirements.
|
|
|
|
<Columns cols={2}>
|
|
<Card title="Self-host with Docker" icon="docker" href="/administration/self-host-docker">
|
|
Compose-first walkthrough. Same image works on ECS, Cloud Run, and Kubernetes.
|
|
</Card>
|
|
<Card title="Deploy to Railway" icon="train" href="/administration/deploy-railway">
|
|
One-click managed shortcut for the same Docker image.
|
|
</Card>
|
|
</Columns>
|