thandClaude Opus 4.7
7bce6a3a36
Central support desk for the Oumta project. Tickets arrive through a
self-hostable support-relay (public form, SMTP out), hyprcrd pulls
them in as cards, replies go back out through the relay, and KB
fragments are plain hyprcrd cards so the board + search + tags
machinery handles them for free.
support-relay/ (standalone PHP/SQLite service)
- Public form + submit endpoint with IP rate-limit, honeypot, and an
email-matched reply path so users can follow up by typing their
OUMTA-n issue id — mismatched email falls back to a fresh ticket
so a hostile submitter can't hijack someone else's thread.
- One-shot setup wizard configures branding, issue-id prefix, public
URL, mail footer template, SMTP creds (stored AES-256-GCM at rest),
and generates the X-Support-Key API token shown exactly once.
- Hyprcrd-facing API: GET /api/hyprcrd/tickets?since=<iso>, POST
…/reply (sends via SMTP, flips status to answered), PATCH
…/status, DELETE, GET /ping, plus GET/POST /api/hyprcrd/settings
exposing brand/public_url/mail_footer for post-setup edits.
- Minimal dependency-free SMTP client covering STARTTLS/TLS/none,
AUTH LOGIN, RFC 2047 subject encoding, dot-stuffing. Extended to
emit multipart/alternative (plain+HTML) + multipart/related so
outbound mails carry the branded logo via Content-ID embedding;
plain-text fallback stays intact for older clients.
- Mail footer template supports {brand}, {issue_id}, {public_url}
placeholders. Lines with an empty placeholder are dropped, so the
"Reply via …" line vanishes cleanly when no public URL is set.
- Favicon on all public pages. Logo (SVG by default, PNG preferred
when both exist) picked up from logo2026col.* at send time.
- Docker: Dockerfile + docker-compose.yml for a stand-alone test
container, plus a support-relay service in the main compose
(profile "support") so hyprcrd can reach it at http://support-relay
without host-networking shenanigans.
public/plugins/support (hyprcrd client)
- Full-screen Support overlay: ticket list (status-filterable),
active ticket thread, reply composer with KB-fragment search +
click-to-insert, "Save as fragment" button, "Close ticket" shortcut.
- KB fragments are regular cards in a configurable bucket. The
composer just adds a fast search-and-insert path on top.
- Sync-tick hook auto-polls the relay alongside the existing CalDAV
+ relay-mail cycle.
- Settings tab in the main overlay: relay URL, API key, inbox / KB
bucket pickers, connection test, and a "Relay config" subsection
that round-trips to /api/hyprcrd/settings so the mail footer and
branding can be edited without touching the relay's DB.
- Local cache tables support_tickets + support_replies mirror the
relay's authoritative data keyed by relay_id.
Tooling
- dev.sh now opts into both relay + support profiles.
- dev-down.sh wipes support-relay volumes and bind-mount data for a
clean re-setup. Hyprcrd + relay data is preserved.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
39 lines
1.5 KiB
Bash
Executable File
39 lines
1.5 KiB
Bash
Executable File
#!/bin/bash
|
|
# Tear down the full dev stack and wipe the support-relay data (DB +
|
|
# master key). Hyprcrd and the main relay keep their data — this is
|
|
# meant for iterating on support-relay setup / API-key rotation.
|
|
#
|
|
# Usage: ./dev-down.sh
|
|
|
|
set -e
|
|
cd "$(dirname "$0")"
|
|
|
|
# If the stand-alone support-relay/docker-compose.yml was used earlier
|
|
# (before we folded it into the main compose), stop that too.
|
|
if [ -f support-relay/docker-compose.yml ]; then
|
|
( cd support-relay && docker compose down --remove-orphans ) 2>/dev/null || true
|
|
fi
|
|
|
|
# Stop main dev stack across all profiles. `down` without -v preserves
|
|
# the named volumes (hyprcrd + relay data).
|
|
docker compose --profile relay --profile support down --remove-orphans
|
|
|
|
# Wipe support-relay storage — both the compose-managed named volume
|
|
# and the stand-alone bind-mount location. Match volumes by suffix so
|
|
# whatever compose-project-name was in effect (hyprcrd / something else)
|
|
# we find it.
|
|
for vol in $(docker volume ls -q | grep -E '(^|_)support-relay-data$' || true); do
|
|
docker volume rm -f "$vol" >/dev/null
|
|
echo " wiped volume: $vol"
|
|
done
|
|
if [ -d support-relay/data ]; then
|
|
rm -f support-relay/data/*.db support-relay/data/*.db-* support-relay/data/master.key 2>/dev/null || true
|
|
echo " wiped bind-mount: support-relay/data/"
|
|
fi
|
|
|
|
echo ""
|
|
echo " all containers stopped."
|
|
echo " support-relay data gone — next boot runs the setup wizard again"
|
|
echo " and mints a fresh API key."
|
|
echo " hyprcrd + relay data preserved."
|