golang-standards/project-layout
wtf
Our great sponsors
| golang-standards/project-layout | wtf | |
|---|---|---|
| 195 | 48 | |
| 45,852 | 1,534 | |
| 2.2% | - | |
| 6.4 | 0.0 | |
| about 2 months ago | over 1 year ago | |
| Makefile | Go | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
golang-standards/project-layout
-
The power of the CLI with Golang and Cobra CLI
cmd: here where we will leave the main.go that starts our app.
-
What's your go to literature to build Go libraries?
> https://github.com/golang-standards/project-layout
The name of the repo is really and intentionally misleading. rsc filled an issue there to point this out, but the repo maintainer just disabled issues altogether so now no one can see it.
Even when it would not have such parasitic name, many seasoned Go programmers, me included, consider the self-proclaimed "Standard Go project Layout" as the opposite of what is good and advisable.
Unfortunately, the name just works, so it is being recommended all over the Internet since its inception.
-
"14 Years of Go" by Rob Pike
Your comment makes it look as if you're saying you hate the Go development team, but it seems that isn't the case.
I get a little of what you're saying, I wouldn't say I hate anyone, but I strongly dislike how a lot of projects are organized. I think a lot stems from https://github.com/golang-standards/project-layout , which pretended to be standard and was so (ab)used one of the creators opened an issue about it. If you look at the actual Go src, it's much, much cleaner.
-
Looking for elegant code bases written in GoLang
So you don't get blind sided for self proclaimed "standards" that are not
- I'm coming from Java and I have been told that I'm writing go like I'm writing Java. Basically creating structs, injecting fields, and attaching methods. What else can I do?
- O poder do CLI com Golang e Cobra CLI
- Como deixar o Swagger com tema dark mode usando Swaggo e Golang
-
Can I point a module to a subdirectory?
I am writing a project that has two components: a CLI and a library. I've organised the project as follows (as per organisation instructions):
-
How To Build A Containerized Microservice in Golang: A Step-by-step Guide with Example Use-Case
Familiarity with the standard Golang project structure, which you can find here.
-
Building RESTful API with Hexagonal Architecture in Go
I've been learning how to build web applications using different frameworks and languages for a while now, such as Laravel with its MVC architecture and Node.js following the 'Hapi.js Way'. As I'm trying to create a new portfolio project using Go, I found myself contemplating over the ideal project structure. I wanted something that not only aligns with the standard Go project layout, but also makes the code both easy to write and understand. That's when I stumbled upon the concept of Hexagonal Architecture, as showcased in Netflix's engineering blog. The idea of seamlessly swapping infrastructures with minimal code changes fascinated me, and I decided to implement it in my new project.
wtf
-
Help with setting up Ben Johnson's wtf repo locally
I am new to go. Found wtf dial - ( https://github.com/benbjohnson/wtf ) while looking to get some project based learning. This looks pretty interesting but when I did git clone of the project my vs code is giving number dependency related problems like below.
-
Educational Codebases
There are a few Go projects meant to be learned from:
- https://github.com/pion/opus for to learn audio
- https://github.com/benbjohnson/wtf for overall production quality
- https://github.com/upspin/upspin difficult to explain, personally I'm not a fan of the errors
- Ben Johnson's WTF project layout: interface usage
- Exemple of Web API written in Go that you'd consider high quality
-
Directory structure for a golang project
I read about https://github.com/benbjohnson/wtf and the connected blog here a couple of times. Seems quite good.
- Project structure - I often see duplicate function names in db layers, why?
-
The one-and-only, must-have, eternal Go project layout
Personally I think the method is the layered architecture approach. Example: https://github.com/benbjohnson/wtf
-
Examples of Good Go Repos
Take a look at the discussions in the repo: https://github.com/benbjohnson/wtf/discussions
-
Examples of an idiomatic API project
https://github.com/benbjohnson/wtf This repo serves as an example and fits Go very well in my opinion. Check the discussions on the repo and the blog posts.
- what do you use for migrations? or how do you the sql tables and seeding?
What are some alternatives?
uber-go-style-guide-kr - Uber's Go Style Guide Official Translation in Korean. Linked to the uber-go/guide as a part of contributions
go-clean-arch - Go (Golang) Clean Architecture based on Reading Uncle Bob's Clean Architecture
modern-go-application - Modern Go Application example
pkgsite - [mirror] Home of the pkg.go.dev website
uber-go-style-guide-th - Uber's Go Style Guide Translation in Thai. Linked to the uber-go/guide as a part of contributions https://github.com/uber-go/guide
Golang-Project-Structure - Golang Skeleton With Fully Managed Versions For Kick Start GoLang Project Development
go-restful-api - An idiomatic Go REST API starter kit (boilerplate) following the SOLID principles and Clean Architecture
bbolt - An embedded key/value database for Go.
cookiecutter-golang - A Go project template
go-clean-template - Clean Architecture template for Golang services
service - Starter-kit for writing services in Go using Kubernetes.
go-webapp-example - Example web application written in Go