Goxygen: The Full-Stack Go Scaffolder That Actually Gets You to Production
Hook
Most project generators leave you with a broken Docker setup and three hours of dependency debugging. Goxygen generates a full-stack application that actually runs with ‘docker compose up’ on the first try.
Context
Setting up a modern full-stack web project is tedious archaeology. You spend a morning wiring up a Go HTTP server, another hour configuring CORS for your React app, then lose an afternoon making Docker Compose orchestrate three containers correctly. By the time you’ve debugged database connection strings across development and production environments, you’ve burned half a sprint on scaffolding.
Goxygen cuts through this setup tax. It’s a CLI generator that produces complete full-stack projects with Go backends and your choice of Angular, React, or Vue frontends. Unlike framework-heavy scaffolders that lock you into opinionated architectures, Goxygen generates minimal, readable code with Docker configurations that work out of the box. The entire tool is distributed as a Go module you run directly—no installation, no version management, just ‘go run github.com/shpota/goxygen@latest init my-app’ and you have a working application.
Technical Insight
Goxygen’s architecture is straightforward: it generates a complete project structure with backend, frontend, and infrastructure code. The generator supports nine combinations—three frontend frameworks (Angular, React, Vue) paired with three databases (MongoDB, MySQL, PostgreSQL)—but maintains simplicity by keeping the backend structure consistent.
The generated Go backend follows clean separation of concerns. Here’s the typical structure for a React/MongoDB project:
server/
├── db/ # Database client and operations
├── model/ # Domain objects (User, Product, etc.)
├── web/ # HTTP handlers and routing
├── server.go # Application entry point
└── go.mod # DependenciesThe backend uses minimal dependencies—only database drivers on the backend and axios for React/Vue projects (Angular uses only Angular-specific libraries). Database operations are isolated in the ‘db’ package, making it straightforward to modify. The ‘web’ package handles REST endpoints, and ‘model’ defines your domain objects.
The frontend follows framework conventions but includes integration details. For React projects, Goxygen generates separate environment files (.env.development and .env.production) that handle the common pain point of API endpoints: your development environment hits the Go server directly, while production routes through a reverse proxy. The generated Dockerfile handles this by building both backend and frontend into a single container, with the Go server serving static frontend assets in production.
The Docker setup includes docker-compose.yml for production deployment and docker-compose-dev.yml for local development with the database. The README mentions that for MongoDB projects, an init-db.js file creates a collection with test data. The generator appears to use template-based generation to produce all project files, allowing the tool to be distributed as a single ‘go run’ command without external dependencies.
Gotcha
Goxygen’s minimalism is both its strength and limitation. The generated code provides basic REST API patterns but doesn’t include authentication, authorization, input validation, or advanced error handling. If you need OAuth2 flows, JWT middleware, or role-based access control, you’re implementing those from scratch.
The generator is a one-shot operation. You choose your frontend framework and database at generation time, and changing either later means manually refactoring multiple files: Dockerfile layers, docker-compose service definitions, backend database clients, and environment configurations. There’s no migration command to evolve your stack.
The project structure is opinionated in subtle ways. The monorepo approach (backend and frontend in one repository) works well for small teams and MVPs but may conflict with enterprise standards that separate services into distinct repositories. The single Dockerfile builds both tiers, which is convenient for simple deployments but doesn’t scale to microservices architectures where you’d want independent backend and frontend containers. If your production environment uses Kubernetes with separate deployment manifests for each service, you’ll need to refactor the Docker setup significantly.
Verdict
Use Goxygen if you’re starting a new full-stack Go project and want to skip directly to writing business logic. It’s perfect for hackathons, MVPs, learning projects, or when you need a clean foundation without framework lock-in. The generated code is readable enough to serve as a learning resource for Go+React/Angular/Vue integration patterns. Use it when you value getting to ‘docker compose up’ working in 30 seconds over having every architectural decision pre-made for you. Skip it if you need authentication and advanced features out of the box, if you’re building microservices that require separate backend/frontend containers, if your team has established project structures that differ significantly from Goxygen’s layout, or if you’re not using Docker for development. Also skip it if you need frameworks beyond the three supported frontends—if you want Svelte, Next.js, or htmx, you’re setting up manually anyway.
