An invite-only Secure Scuttlebutt pub for Manyverse. It follows invited identities and stores their classic SSB feeds and requested blobs, so other invited peers can sync while the original author is offline.
The server uses the same versions of ssb-db2, ssb-ebt and ssb-blobs as Manyverse. Replication on the pub is limited to its own feed and the identities it follows directly. Readers can follow individual authors in Manyverse to fetch their posts.
For a public pub, run these commands and set PUB_URL in .env to your HTTPS origin.
cp .env.example .env
docker compose up -d --build --wait
docker compose exec pub /app/code/pubctl invitePoint the DNS name at your HTTPS reverse proxy and forward requests to 127.0.0.1:3000, including WebSocket upgrades on /. For example, with Caddy running on the same host:
pub.example.com {
reverse_proxy 127.0.0.1:3000
}If you enable password sign-in behind a Compose reverse proxy, set PUB_TRUSTED_PROXY to the proxy's source IP as seen by the container. The proxy must append or overwrite X-Forwarded-For with the connecting client's IP. Cloudron supplies its trusted proxy IP automatically.
Paste the resulting link under Connections → Paste invite code in Manyverse. Each link can enroll one identity and expires after seven days. The same identity can retry during that time. The operator can show the pub ID and advertised address with docker compose exec pub /app/code/pubctl status.
For a local check, run Compose without an .env and open http://127.0.0.1:3000. Use an HTTPS URL for Manyverse invitations.
To use plain TCP as the SSB transport, set SSB_PORT in .env if port 8008 is already in use and start with both Compose files. Use the same file arguments on subsequent Compose commands.
docker compose -f compose.yaml -f compose.tcp.yaml up -d --build --wait
docker compose -f compose.yaml -f compose.tcp.yaml exec pub /app/code/pubctl inviteThe invitation remains an HTTPS link and Manyverse then connects via the advertised TCP port using SSB’s encrypted handshake. Open the chosen TCP port on your firewall and use a DNS record that resolves directly to the server. WebSocket invitations use the default Compose configuration. Clients that support only the original host:port:@key~seed invitation format are outside this release’s compatibility.
In Cloudron, open App Store → Add custom app → Community app and paste the SSB Pub install URL.
https://raw.githubusercontent.com/patattzel/ssb-pub/main/CloudronVersions.json
Choose a domain. The Cloudron manifest defaults to WebSockets over HTTPS. For a CLI installation, substitute your Cloudron and app domains:
cloudron login my.example.com
cloudron install --location pub.example.com --port-bindings SSB_PORT=x --versions-url https://raw.githubusercontent.com/patattzel/ssb-pub/main/CloudronVersions.jsonFor TCP, enable the Direct SSB TCP port on Cloudron or install with --port-bindings SSB_PORT=18008 using a free port. Use a DNS-only record for a TCP endpoint behind Cloudflare.
- Copy your public SSB ID from your Manyverse profile. It starts with
@and ends with.ed25519. - In Cloudron’s Web Terminal, run
/app/code/pubctl adminand paste the ID. With Compose, rundocker compose exec pub /app/code/pubctl admin. - Open the pub, choose Admin sign-in → Open Manyverse, and approve the login in Manyverse. To sign in using a phone, open Use Manyverse on another device and scan the QR code. Keep the original browser open.
- Under Pub settings, change the name, description and image or create an invite. Saving the profile publishes a signed SSB
aboutmessage and stores the image as an SSB blob, so peers replicating the pub’s feed can see the profile in Manyverse.
To enable or reset the password fallback, run /app/code/pubctl password in the same terminal. Admin sign-in then offers a password form. Resetting the password signs out existing web sessions. Running pubctl admin with a different ID replaces the administrator, clears the fallback password and signs out old sessions. Upgrading from 0.1.0 keeps the existing pub identity, replicated data and invitations.
Update the version and changelog in CloudronManifest.json. A matching cloudron-v<version> Git tag triggers the image build, container checks and push to GitHub Container Registry. Verify public pull access and add the new image to the catalog by digest:
cloudron versions add --image ghcr.io/patattzel/ssb-pub@sha256:DIGEST
cloudron versions verifyCommit and push the updated CloudronVersions.json to main.
The Compose volume pub-data keeps the pub identity, feeds, blobs, EBT state, invitations and admin credentials across rebuilds. Cloudron keeps these under /app/data/ssb-pub and uses SQLite-aware backups for invitations and admin settings. For a consistent filesystem snapshot of the full data directory, stop the pub before copying. Keep the directory together when restoring, and keep backups private because they include the identity key.
If an installed 0.1.0 or 0.2.0 app reports Cannot find module '/app/code/sqlite3' before an update, use the Cloudron CLI to replace the running image. Repair restarts the app with the same data and installs the image that Cloudron needs for the backup. Use the same digest as the catalog entry so Cloudron retains the image when it replaces the container. Then apply the catalog update with the usual pre-update backup. Replace the two example domains with your dashboard and pub domains.
cloudron login my.example.com
versions_url=https://raw.githubusercontent.com/patattzel/ssb-pub/main/CloudronVersions.json
image=$(curl -fsS "$versions_url" | jq -er '.versions["0.2.1"].manifest.dockerImage')
cloudron repair --app pub.example.com --image "$image"
cloudron update --app pub.example.com --versions-url "$versions_url"If a previous attempt repaired the app by tag and the update now reports No such image for the catalog digest, pull that exact digest with sudo docker pull "$image" on the Cloudron host. Then open the app's Repair page and retry the failed task.
Use Node.js 24, then run npm ci and npm test. The integration tests use the Manyverse HTTP auth and invite clients and replication scheduler. They exercise admin sign-in, profile editing, invitation claim, joining via WebSocket and TCP, EBT feed replication, blob retrieval and persistence across a restart.