Web-app-seaweedfs Role¶
Description: Distributed S3-compatible object store for shared, per-consumer bucket provisioning across web-app roles
Variables¶
author: Kevin Veen-Birkenbach
description: Distributed S3-compatible object store for shared, per-consumer bucket provisioning across web-app roles
license: Infinito.Nexus Community License (Non-Commercial)
company: Kevin Veen-Birkenbach https://www.veen.world
min_ansible_version: 2.9
platforms: [{‘name’: ‘ArchLinux’, ‘versions’: [‘all’]}, {‘name’: ‘Debian’, ‘versions’: [‘all’]}, {‘name’: ‘EL’, ‘versions’: [‘all’]}, {‘name’: ‘Fedora’, ‘versions’: [‘all’]}, {‘name’: ‘Ubuntu’, ‘versions’: [‘all’]}]
galaxy_tags: [‘seaweedfs’, ‘objectstore’, ‘s3’, ‘storage’, ‘docker’]
README¶
SeaweedFS¶
Description¶
SeaweedFS is a fast distributed storage system for blobs, objects, and files. It exposes an S3-compatible API, so applications store and retrieve objects with standard S3 SDKs and CLIs.
Overview¶
This role deploys SeaweedFS as the central provider of the project-wide
object-store service (engine seaweedfs). Web-app roles consume it
like a database: they enable a seaweedfs service in their
meta/services.yml and resolve host, port, bucket, and credentials
through the objstore lookup. A single server container runs master,
volume, filer, and the S3 gateway in one process, accompanied by an
nginx sidecar that routes the admin UIs. The role serves three canonical
domains:
api.seaweedfs.s3.*is the public S3 endpoint and is reachable without SSO gating.filer.seaweedfs.s3.*serves the filer web UI behind an admin-only oauth2-proxy.master.seaweedfs.s3.*serves the master web UI behind the same admin-only oauth2-proxy.
Per-consumer S3 identities are rendered into s3.json: each consuming
role receives an access key and bucket-scoped Read, Write,
WriteAcp, List, and Tagging actions, and consumers marked
public additionally receive anonymous read on their bucket. Consumer
buckets are created through weed shell when a consumer role requests
provisioning. The bucket of every consumer not marked public carries
a bucket policy statement DenyAnonymousRead that denies all unsigned
reads, so a public-read ACL set by an app never exposes an object;
signed and presigned requests are unaffected. Every deploy of this role
converges that statement on all existing consumer buckets, adding it to
private buckets and removing it from public ones, and a consumer’s
provisioning applies it right after creating the bucket. Other
statements an operator adds to a consumer’s bucket policy are kept.
In embedded mode (shared: false) a consumer’s compose stack receives
a storage-only SeaweedFS container without UI or published ports. The
embedded S3 listener starts without identities and accepts
unauthenticated requests until the background s3.configure grant at
startup registers the consumer identity; from then on it authenticates
against that identity. Embedded buckets carry no DenyAnonymousRead
statement because the listener publishes no port, so the container MUST
stay confined to the consumer’s isolated compose network.
Cosmos¶
The diagram places SeaweedFS in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
flowchart LR
subgraph deps [Dependencies]
dep_svc_bkp_volume_2_local["svc-bkp-volume-2-local 💻"]
dep_svc_db_openldap["svc-db-openldap 🐳🐝"]
dep_web_app_dashboard["web-app-dashboard 🐳🐝"]
dep_web_app_keycloak["web-app-keycloak 🐳🐝"]
dep_web_app_prometheus["web-app-prometheus 🐳🐝"]
dep_web_svc_logout["web-svc-logout 🐳🐝"]
end
subgraph role [web-app-seaweedfs 🐳🐝]
svc_frontend["frontend"]
svc_sso["sso"]
svc_ldap["ldap ❌"]
svc_logout["logout"]
svc_dashboard["dashboard"]
svc_prometheus["prometheus"]
svc_seaweedfs["seaweedfs"]
svc_proxy["proxy"]
svc_container_backup["container_backup"]
end
subgraph dependents [Dependents]
dpt_web_app_akaunting["web-app-akaunting 🐳🐝"]
dpt_web_app_baserow["web-app-baserow 🐳🐝"]
dpt_web_app_bookwyrm["web-app-bookwyrm 🐳🐝"]
dpt_web_app_decidim["web-app-decidim 🐳🐝"]
dpt_web_app_fider["web-app-fider 🐳🐝"]
dpt_web_app_funkwhale["web-app-funkwhale 🐳🐝"]
dpt_web_app_gitea["web-app-gitea 🐳🐝"]
dpt_web_app_gitlab["web-app-gitlab 🐳🐝"]
dpt_web_app_listmonk["web-app-listmonk 🐳🐝"]
dpt_web_app_magento["web-app-magento 🐳🐝"]
dpt_web_app_mastodon["web-app-mastodon 🐳🐝"]
dpt_web_app_matrix["web-app-matrix 🐳🐝"]
dpt_more["..."]
end
dep_svc_bkp_volume_2_local -. "0..1" .-> svc_container_backup
dep_svc_db_openldap -- "0..0" --> svc_ldap
dep_web_app_dashboard -. "0..1" .-> svc_dashboard
dep_web_app_keycloak -. "0..1" .-> svc_sso
dep_web_app_prometheus -. "0..1" .-> svc_prometheus
dep_web_svc_logout -. "0..1" .-> svc_logout
svc_frontend -- "1:1" --> dpt_more
svc_frontend -. "0..1" .-> dpt_web_app_akaunting
svc_frontend -. "0..1" .-> dpt_web_app_baserow
svc_frontend -. "0..1" .-> dpt_web_app_bookwyrm
svc_frontend -. "0..1" .-> dpt_web_app_decidim
svc_frontend -. "0..1" .-> dpt_web_app_fider
svc_frontend -. "0..1" .-> dpt_web_app_funkwhale
svc_frontend -. "0..1" .-> dpt_web_app_gitea
svc_frontend -. "0..1" .-> dpt_web_app_gitlab
svc_frontend -. "0..1" .-> dpt_web_app_listmonk
svc_frontend -. "0..1" .-> dpt_web_app_magento
svc_frontend -. "0..1" .-> dpt_web_app_mastodon
svc_frontend -. "0..1" .-> dpt_web_app_matrix
linkStyle 1 stroke:red;Solid 1:1 edges are fixed relationships; dashed 0..1 edges are
conditional (enabled only in matching deployments); red 0..0 edges
are turned off in this role. Node markers show the role’s deploy modes
(💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly
turned off, and ⚙️ an Ansible role dependency declared in
meta/main.yml.
Features¶
S3-compatible API: Standard S3 SDKs and CLIs work against the gateway for uploads, media, attachments, and exports.
Central object-store service: One shared instance serves all consuming web-app roles, mirroring the shared database pattern.
Per-consumer isolation: Every consumer receives its own identity and bucket with bucket-scoped actions only.
Admin-gated UIs: The filer and master web interfaces are reachable only for members of the administrator group via oauth2-proxy.
Embedded mode: Roles that opt out of the shared instance run a private storage-only container inside their own compose network.
Quick Setup¶
Development¶
Clone, set up the workstation, and deploy SeaweedFS onto the local stack:
git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=web-app-seaweedfs full_cycle=false
Production¶
Run the published image to provision the inventory and deploy SeaweedFS to a managed server (the mounted volume persists the inventory):
APP=web-app-seaweedfs
HOST=<your-server>
DOMAIN=<your-domain>
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"
docker run --rm -it \
-v "$PWD/inventories:/etc/infinito.nexus/inventories" \
-e APP="$APP" -e HOST="$HOST" -e DOMAIN="$DOMAIN" -e TLS_MODE="$TLS_MODE" -e SSH_PUBLIC_KEY="$SSH_PUBLIC_KEY" \
ghcr.io/infinito-nexus/core/debian bash -c '
INVENTORY=/etc/infinito.nexus/inventories/production
infinito administration inventory provision "$INVENTORY" \
--inventory-file "$INVENTORY/devices.yml" \
--host "$HOST" \
--include "$APP" \
--vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}" &&
infinito administration deploy dedicated "$INVENTORY/devices.yml" \
--password-file "$INVENTORY/.password" \
--diff -vv'
Further Resources¶
Credits¶
Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).