Run your own server
Coming with the first open-source release. This is how it will work; the container image isn't published yet.
An LGU, a federation, a school or a network of chapters can run its own Bayanihan Server, keep its records on its own machine, and still list its groups on the Dasig Ecosystem if it wants to.
What you need
- A small Linux server: 1 GB of memory is enough for many groups.
- Docker.
- Any S3-compatible storage for backups: AWS S3, Cloudflare R2, Backblaze B2, or MinIO on your own hardware.
- A domain name.
The stack
- Bayanihan Server on SQLite: one container, one database file. The same store runs inside every phone.
- Litestream streams every change in the database to your storage within seconds. Restoring onto a new server is one command.
- Caddy serves it over HTTPS with automatic certificates.
# docker-compose.yml (preview)
services:
bayanihan:
image: bayanihan/server:0.1
environment:
BIX_DB: /data/bix.db
volumes: [ "data:/data" ]
litestream:
image: litestream/litestream
command: replicate
volumes: [ "data:/data", "./litestream.yml:/etc/litestream.yml" ]
caddy:
image: caddy:2
ports: [ "80:80", "443:443" ]
volumes: [ "./Caddyfile:/etc/caddy/Caddyfile" ]
volumes:
data:Growing
When one server isn't enough, point Bayanihan Server at PostgreSQL instead. It supports both, and the records are the same BIX either way.
Your own policy
A host sets its own rules for who can join and what it checks. The Dasig Ecosystem's host policy is one example you can start from.