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
Karrot
Karrot is a community platform for sharing resources, coordinating food-saving activities, and organizing volunteers. Groups can manage pickups, track saved food, and communicate through a shared feed.
Dependencies
- PostgreSQL - Database for storing groups, users, and activity data
- SMTP - For account verification and notifications
Configuration
Key settings in config.yaml:
- domain - Where Karrot will be accessible (default:
karrot.{your-cloud-domain}) - storage - Persistent volume size for uploaded files (default:
2Gi) - redis.host - Redis instance for caching and background jobs (default: app-local
karrot-redis) - smtp - Email settings inherited from your Wild Cloud SMTP service
First-Time Setup
-
Add and deploy the app:
wild app add karrot wild app deploy karrot -
Visit
https://karrot.{your-cloud-domain}and register an account. The first user to register becomes the site admin. -
Log in and create your first group to start coordinating.
Notes
- Karrot supports federation — groups can connect with other Karrot instances
- The
secretKeyanddbPasswordare auto-generated insecrets.yaml - Uploaded files (photos, attachments) are stored in the persistent volume and shared between the frontend and backend pods