goyek
golang-standards/project-layout
Our great sponsors
goyek | golang-standards/project-layout | |
---|---|---|
10 | 195 | |
504 | 45,852 | |
3.2% | 2.2% | |
7.9 | 6.4 | |
7 days ago | about 2 months ago | |
Go | Makefile | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
goyek
- Goyek: Build Automation in Go
-
Reason to use other Build Tool than Make?
You can also take a look at https://github.com/goyek/goyek. Personally I use either Make or goyek. Disclaimer: I am the author of goyek
-
Is your makefile supposed to be a justfile?
I think that Make is so popular, because Go comes from C. Many C and C++ devs migrated to Go. Personally, I created goyek as an alternative.
-
Task runner like go-task/task, but in pure Go, no external DSLs
how about https://github.com/goyek/goyek
-
Build\task automation in Go
It's also what I'm using currently as direct make/makefile replacement. What I plan to use next time though is goyek: https://github.com/goyek/goyek . Concept looks really nice but I haven't tried it yet in any real case scenario.
-
goyek v2 is coming soon
https://github.com/goyek/goyek v2.0.0 is to be released in two months. Now it is the best time to provide feedback.
-
goyek v2 RC - feedback needed
In my "free time" I develop https://github.com/goyek/goyek
- goyek v1.0.0 is released
-
goyek is looking for feedback before going v1
https://github.com/goyek/goyek (initially `taskflow`) first release was more than a year ago. So far been slightly improved.
-
The first release of goyek - a library for creating build pipelines
Check out: https://github.com/goyek/goyek#make Also reusing Make targets between multiple repositories is harder (e.g. via git submodules) Here are some presentation if you are more interested: https://github.com/goyek/goyek#presentations
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.
What are some alternatives?
mage - a Make/rake-like dev tool using Go
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
taskflow - Create build pipelines in Go [Moved to: https://github.com/goyek/goyek]
modern-go-application - Modern Go Application example
golang-templates/seed - Go application GitHub repository template.
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
weaver - Programming framework for writing and deploying cloud applications.
go-restful-api - An idiomatic Go REST API starter kit (boilerplate) following the SOLID principles and Clean Architecture
Task - A task runner / simpler Make alternative written in Go
cookiecutter-golang - A Go project template
pants - The Pants Build System
service - Starter-kit for writing services in Go using Kubernetes.