34 lines
1.2 KiB
Markdown
34 lines
1.2 KiB
Markdown
# 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
|
|
|
|
1. Add and deploy the app:
|
|
```bash
|
|
wild app add gancio
|
|
wild app deploy gancio
|
|
```
|
|
|
|
2. Visit the app URL — on first load, a setup wizard will run to create the admin account and configure the instance.
|
|
|
|
3. 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. Fix by dropping and recreating the public schema in the `gancio` database before restarting. See ADDING-APPS-NOTES.md note 18 for the exact commands.
|
|
- Gancio stores its setup state in `config.json` on the data PVC — do not delete the PVC without also clearing the database
|
|
- Events are federated to Mastodon and other ActivityPub platforms
|