Install SeaweedFS on your VPS
Infraa installs SeaweedFS on your VPS as a single Go binary running master, volume server, filer, and S3 gateway in one process — S3-compatible object storage on your own hardware. The binary (4.38) is pinned and verified against a checked-in SHA-256, runs as a dedicated non-root system user, and binds everything to localhost, with the S3 API on port 8333.
- Versions
- SeaweedFS 4.38, a pinned single-binary release verified by SHA-256
- Works on
- Ubuntu 22.04, Ubuntu 24.04, and Debian 12
- Package source
- Pinned binary release
What does the SeaweedFS install do?
- Creates a dedicated, non-login system user (infraa-seaweedfs) — SeaweedFS never runs as root.
- Downloads the pinned weed binary, verifying it against a SHA-256 checksum from the reviewed catalog before it's moved into place.
- Installs a systemd unit (infraa-seaweedfs.service) that runs all components bound to 127.0.0.1 — the S3 API on your chosen port (8333 by default), master, volume, and filer on their internal defaults — with object data in /var/lib/infraa-seaweedfs.
- Enables and starts the service, then verifies the S3 endpoint is listening.
How do I install SeaweedFS with Infraa?
Connect your server
Run the Infraa install one-liner (curl install.infraa.sh | sh) on your VPS. The agent registers over an outbound connection in about 30 seconds — no inbound ports, no SSH keys to share.
Pick the service
Choose it from the one-click catalog in the dashboard, or just ask in chat. Infraa turns your request into a concrete, reviewable plan.
Review and approve
Read exactly what will run, then approve. The agent executes only the approved, cryptographically signed steps and streams progress live.
What happens after the install?
Infraa checks SeaweedFS every 60 seconds — the service unit and the S3 port. Apps on the same server use 127.0.0.1:8333 with any S3 client or SDK; to serve remote clients, install the nginx module and put a managed vhost with Let's Encrypt in front of the S3 port.
SeaweedFS on Infraa — common questions
01Is SeaweedFS really S3-compatible?
Yes — it exposes an S3-compatible API on port 8333, so standard S3 SDKs and tools (aws-cli, rclone, MinIO clients) work by pointing their endpoint at it. It's a common way to keep S3-shaped workloads on your own hardware.
02Where do my objects live?
In /var/lib/infraa-seaweedfs, owned by the dedicated system user. Object data survives restarts and binary upgrades — re-installing replaces the pinned binary without touching the store.
03Why does SeaweedFS open four ports?
One process runs four components: the S3 gateway (8333) you actually use, plus the master (9333), volume server (8080), and filer (8888) as internal plumbing. All four are bound to 127.0.0.1 — nothing listens publicly.
Connect a server in 30 seconds, then install SeaweedFS from the catalog or just ask in chat.
