kevinveenbirkenbachandClaude Opus 5
4986e80dd4
The Production block never set one. inventory provision writes only
ansible_connection for a local host, so DOMAIN_PRIMARY stayed at the
group_vars default of infinito.localhost and the deployment served a zone its
own resolver knows nothing about. CoreDNS templates answers for
INFINITO_DOMAIN_RE and nothing else, so every lookup of the deployment's own
name came back NXDOMAIN.
Mastodon is where that surfaced. tootctl accounts create validates the address
through EmailMxValidator, which resolves MX and then, for the domain itself,
A and AAAA. All six queries returned NXDOMAIN in run 33574056480, the
validator recorded email :unreachable, and the admin account was never created.
Only the guide rows were affected: the matrix rows write
DOMAIN_PRIMARY: "{{ lookup('env', 'INFINITO_DOMAIN') }}" into their host_vars
and resolve fine.
The template now carries DOMAIN=<your-domain> in both the host and the
container form and threads it into --vars, with the container form passing it
through the docker run boundary as well. The two guide runners substitute it
the way they already substitute the SSH key, so the replay deploys under
INFINITO_DOMAIN like every other CI deploy. compose_deploy.sh moves its env
load ahead of the substitutions to have the value; host_deploy.sh had no env
load at all.
A production reader is asked for a domain now instead of silently inheriting
infinito.localhost, which no real deployment wants either. The shipped default
keeps its value: sys-svc-nss documents that *.localhost resolves through the
myhostname NSS module without any zone, and host-side tasks lean on it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
7.1 KiB
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, 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.
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 performs no authentication, so it 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).