Matthew Knight
51eeb4c9c1
Reviewed-on: https://git.ts.mattnite.net/mattnite/forgejo-tickets/pulls/63 |
||
|---|---|---|
| .forgejo/workflows | ||
| cmd/server | ||
| docs | ||
| internal | ||
| web | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| Dockerfile | ||
| Makefile | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
| package-lock.json | ||
| package.json | ||
README.md
Forgejo Tickets
A customer-facing support ticket system that bridges a web UI with Forgejo issue tracking. Customers create and manage support tickets through a clean web interface, while tickets automatically sync to Forgejo repositories as issues for internal team tracking.
Quick Start
cp .env.example .env
# Edit .env with your database URL, session secret, etc.
make build
make run
The public server starts on :8080 and the admin server on :8081.
Documentation
| Topic | Description |
|---|---|
| Architecture | Two-server design, directory structure, package responsibilities, request lifecycle |
| Configuration | Full environment variable reference with defaults and descriptions |
| Deployment | Local dev, Docker, Nomad, Makefile targets, database setup |
| User Guide | Registration, login, tickets, comments, email notifications |
| Admin Guide | Dashboard, user/ticket/repo management, Tailscale auth |
| Forgejo Integration | Issue sync, comment sync, webhooks, auto-close flow |
| SSO Integration | JWT SSO with Ed25519 for auto-provisioning users from external apps |