feat(synapse): update ingress to use traefik ingress class and bump version feat(syncthing-discovery): introduce syncthing discovery service with deployment and ingress feat(syncthing-relay): add syncthing relay server with deployment and ingress configuration fix(taiga): update liveness and readiness probes to use tcpSocket for health checks fix(taiga): change PVC access mode to ReadWriteMany for media and static storage feat(traefik): add icon and ignore rules for traefik service docs(ushahidi): add notes for Redis configuration and Laravel startup probe adjustments feat(ushahidi): implement dedicated Redis deployment for Ushahidi fix(vllm): update deployment strategy and readiness/liveness probes for improved stability fix(writefreely): pin writefreely image version to v0.15.1 for consistency docs(zulip): add notes for TLS-terminating reverse proxy configuration and expected behavior
Gancio
Gancio is a shared agenda for local communities, federated via ActivityPub. It allows groups to publish and discover local events.
Dependencies
- PostgreSQL - Database for storing events and users
Configuration
Key settings in config.yaml:
- domain - Where Gancio will be accessible
- storage - Persistent volume size (default:
2Gi) - db.name - Database name (default:
gancio)
First-Time Setup
-
Add and deploy the app:
wild app add gancio wild app deploy gancio -
Visit the app URL — on first load, a setup wizard will run to create the admin account and configure the instance.
-
After setup, you can start publishing events and inviting community members.
Notes
- Re-deploy warning: If the app is deleted and redeployed with an existing database, Gancio will refuse to start with a "Non empty db" error. See
gancio/notes.mdfor the fix. - Gancio stores its setup state in
config.jsonon the data PVC — do not delete the PVC without also clearing the database - Events are federated to Mastodon and other ActivityPub platforms