go-oidc-middleware
golang-standards/project-layout
go-oidc-middleware | golang-standards/project-layout | |
---|---|---|
7 | 195 | |
92 | 45,978 | |
- | 1.3% | |
6.3 | 6.4 | |
5 days ago | about 2 months ago | |
Go | Makefile | |
MIT License | 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.
go-oidc-middleware
- go-oidc-middleware: Breaking change for claims validation
-
Go 1.18 improved benchmarks too much?
You can see the PR here and I attached the logs for the workflow run that did the comparison between the versions: https://github.com/XenitAB/go-oidc-middleware/pull/158
-
Boilerplate for experienced devs
I’ve built a library to try and make it easier to consume these services and their JWTs that works with net/http, mux, chi, gin, echo and fiber if you don’t want to implement the logic of discovery and validation yourself: https://github.com/XenitAB/go-oidc-middleware
-
Question if generics will help with use case
Source: https://github.com/XenitAB/go-oidc-middleware/blob/main/internal/oidc/cty.go
-
[go-oidc-middleware] separate sub-modules and test provider
You can find the module here: https://github.com/XenitAB/go-oidc-middleware
-
go-oidc-middleware: support for mux, chi, gin, echo & fiber
I’ve been spending some free time building a http middleware to make it easy to validate JWT tokens from OpenID Providers: go-oidc-middleware
- go-oidc-middleware: OpenID Connect (OIDC) http middleware for Go
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?
zap - Blazing fast, structured, leveled logging in 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
ent - An entity framework for Go
modern-go-application - Modern Go Application example
go-kit - A standard library for microservices.
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
casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Golang: https://discord.gg/S5UjpzGZjN
go-restful-api - An idiomatic Go REST API starter kit (boilerplate) following the SOLID principles and Clean Architecture
simple_gopher - Boilerplate for writing Go applications without framework using hexagonal application development approach
cookiecutter-golang - A Go project template
jennifer - Jennifer is a code generator for Go
service - Starter-kit for writing services in Go using Kubernetes.