Go to file
Matthew Knight 210fa4ee2d
attachment fixes
2026-02-14 14:11:05 -08:00
cmd/server Forgejo as the source of truth 2026-02-14 02:04:27 -08:00
docs Create docs 2026-02-12 15:20:41 -08:00
internal attachment fixes 2026-02-14 14:11:05 -08:00
web attachment fixes 2026-02-14 14:11:05 -08:00
.dockerignore Init 2026-02-12 15:00:17 -08:00
.env.example Init 2026-02-12 15:00:17 -08:00
.gitignore Init 2026-02-12 15:00:17 -08:00
Dockerfile docker fix 2026-02-13 23:08:55 -08:00
Makefile Init 2026-02-12 15:00:17 -08:00
README.md Create docs 2026-02-12 15:20:41 -08:00
go.mod More forgejo features 2026-02-14 12:59:32 -08:00
go.sum More forgejo features 2026-02-14 12:59:32 -08:00
package-lock.json More forgejo features 2026-02-14 12:59:32 -08:00
package.json More forgejo features 2026-02-14 12:59:32 -08:00

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