kago VS jwt

The closest I’ve seen is https://github.com/kamalshkeir/kago it’s not only building the restful part but also the ORM using Go generics to match día go behavior. It even supports migrations

Feel free to join our discussions https://github.com/kamalshkeir/kago/discussions/7

exactly, chi is a very good router, but still not fit my use cases, so i make my own, that handle extra things i needed to have in my framework https://github.com/kamalshkeir/kago

i hate gin , donno echo very well, but i found that going from stdlib to build a small framework will give you very good experience, and the framework will be adapted to your need, feel free to check kago , a framework like django, very easy to get started with kago

Hello all, It may seem weird , but i will explain. KaGo is my new golang web framework, i deployed a website using it : kamalshkeir.dev , i tried my best to make this framework very secure, but i'm not an expert, that's why i think about this challenge for hacker gophers :p, to be able to find more vulnerabilities before people start using it. I give you all permissions to hack this website, so please feel free to tested like if it was you own website. Thank you all in advance

handle migration from struct , so detect when remove or add field to struct https://github.com/kamalshkeir/kago

https://github.com/kamalshkeir/kago , check the dependencies, you will see that everything is used, you can easily benchmark against gorm and against the standard library for example to compare performance , i have some benchmarks in the readme too

few days ago, i have maid a new portfolio/blog using my framework KaGo. I like to always run my small projects on vps and deploye them from scratch on ubuntu or centos, let's say to not forget my good practices. Long story short, i have never deployed an application using only the binary and systemd with a domain name and ssl, i have always used apache and nginx as proxy behind my app. Look at it now https://kamalshkeir.dev😁😁😁 , my gopher portdolio running listenandserveTLS with letsencrypt certificate, no proxy, no static files no templates , only the binary 9Mb running with systemd on the server. That's not all, my go app was using nothing from the power of my vps , less than 10% , so i said why i don't try grafana, prometheus, loki ..., all these good stuff. And that's why i'm so happy, i have finally the dashboard i have looking for, grafana dashboard , prometheus scraping all metrics from my go application, promtail and loki getting me the logs to the dashboard, node exporter showing me metrics for my linux system, and postgres exporter for my database, all in one place. i you want to look at it, you can 😁 , this is the link to grafana https://kamalshkeir.dev:9999 username: test password: testadmin

https://github.com/kamalshkeir/kago is pretty much like django, 2 min to get up and running

To add JWT authentication to our ToDo application, we'll be using the Golang-jwt library. The golang-jwt package simplifies the implementation of JWTs in Go applications, offering a suite of convenient functions that abstract away the complexities associated with token creation, verification, and management.

golang-jwt/jwt - GitHub

To create a secure Role-based authentication scheme, we need to generate a unique token when the user authenticates. This is then used to track their assigned role as they consume the availed resources. In this project we are going to use the jwt-go package to generate a JWT token that will encapsulate the user details, assigned role and permissions.

Yes. Currently maintained version is here: https://github.com/golang-jwt/jwt

Libraries used bcrypt: https://pkg.go.dev/golang.org/x/crypto/bcrypt golang-jwt: https://github.com/golang-jwt/jwt Gin (Http framework): https://github.com/gin-gonic/gin

We will implement Golang JWT authentication using a go-jwt package.

Authorization jwt

At least template-wise, I've developed pongo2 mimicking Django's template engine which I use myself for various projects. For the rest I usually stick with the standard library (net/http), golang-jwt, the Gorilla toolkit (note that it's been archived recently) and some software architecture patterns for middlewares, database abstraction, etc.

Either way, you will need to validate the signature of the JWT. You can do this with the public key and a library such as https://github.com/golang-jwt/jwt.