Skip to content

Support group v0.1.0 — Planka, Chatwoot (WhatsApp)

Choose a tag to compare

View all tags
@govtech42 govtech42 released this 26 Jun 01:14
support-v0.1.0
1928f88
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Support group — v0.1.0

Planka (kanban) + Chatwoot (helpdesk, WhatsApp Cloud API) on one AWS Lightsail
8 GB host; Chatwoot's own Redis + MinIO attachments; per-group reporting
(FDW views + PostgREST + Adminer); Caddy auto-TLS; N2. Merged via PR #2.

Verified locally (Colima): 14/14 smoke. Chatwoot runs the official image locally;
the fork (code42/chatwoot, += Kanban) builds off-host → GHCR at deploy.

Deploy-time: fork → GHCR; provision host + DNS/TLS; WhatsApp Cloud API channel
in the Chatwoot UI.

Changelog — Support

  • feat(support): Planka + Chatwoot stack (Redis + MinIO) on shared Postgres
  • feat(support reporting): Planka + Chatwoot FDW views + PostgREST/Adminer
  • feat(support): Chatwoot fork Dockerfile (deferred submodule) + RUNBOOK section
  • Add Support group design spec (Planka + Chatwoot, WhatsApp, MinIO)
  • Add implementation plan for Support group (Planka, Chatwoot)

Platform / shared (PR #2)

  • refactor(postgres): group-driven APP_DBS + pgvector base
  • feat(cli): bin/devtools single entrypoint (init / up|down|smoke|reporting --)
  • fix(cli): trim devtools help to the comment block
  • docs(recipes)+skill: capture recurring gotchas for future installs
  • docs: essential repo + .claude markdown
  • chore(conductor): add .conductor/settings.toml (setup/run/archive, nonconcurrent)
  • decision: ingress = Caddy, not Traefik (record rationale + reconsider triggers)
  • roadmap: add Admin group (Twenty CRM, shared Postgres) to backlog
Assets 2
Loading