Go + Gin + PostgreSQL + GORM Starter
Gin, PostgreSQL, GORM, and Zap form a backend service configuration where the generated project is centered on a backend service. Better Fullstack can scaffold this exact compatibility-checked selection.
01 / selection
Stack at a glance
| Role | Technology | Repository description | Scope |
|---|---|---|---|
| Backend | Gin | High-performance HTTP web framework with martini-like API | Primary backend |
| Database | PostgreSQL | Advanced SQL database | Project-wide |
| ORM | GORM | The fantastic ORM library for Golang | Scoped to the backend |
| Logging | Zap | Blazing fast, structured, leveled logging in Go | Scoped to the backend |
02 / architecture
How the pieces fit
- The generated stack is centered on a backend service with no browser frontend.
- GORM is scoped to the backend.
- Zap is scoped to the backend.
03 / output
What gets generated
The virtual generator produced 10 files across 6 directories. The output is a single-directory project.
Top-level entries
- ./.env.example
- ./.gitignore
- ./AGENTS.md
- ./CLAUDE.md
- ./README.md
- ./cmd
- ./go.mod
- ./internal
Representative files
- README.md
- go.mod
- cmd/server/main.go
- .env.example
- .gitignore
- AGENTS.md
- CLAUDE.md
- internal/database/database.go
04 / create
Create command
This is the canonical Bun command generated for the selection.
bun create better-fullstack@latest my-app --ecosystem go --database postgres --go-web-framework gin --go-orm gorm --go-api none --go-cli none --go-logging zap --go-auth none --go-testing none --go-realtime none --go-message-queue none --go-caching none --go-config none --go-observability none --go-validation none --go-quality none --go-migrations none --go-templating none --go-proto-tooling none --go-di none --auth none --email none --observability none --caching none --search none --ai-docs claude-md agents-md05 / builder
Open in the builder
- eco
- go
- db
- postgres
- au
- none
06 / checks
Compatibility notes
Compatibility checked against Better Fullstack types version 2.3.0.
The generated record has 0 graph issues and 0 disabled selected options. This is a compatibility check, not a claim that this exact scaffold received a runtime smoke verification.
07 / fit
When to choose this shape
Choose this shape when the generated project should expose backend functionality without a browser frontend.
08 / next
Related stacks and guide
Need a walkthrough? Read the related stack guide.
09 / faq
Questions
Is this combination supported?
It passes the repository's compatibility analysis, selected-option checks, stack graph validation, project schema parsing, and virtual generation. That result is described here as compatibility checked.
Does it generate one app or separate parts?
The generated project is centered on a backend service. The actual generated output uses a single-directory layout.
How can I customize the selection?
Open the generated builder link above. Its query parameters reproduce this selection, and the builder can change compatible options before generating a new command.