sessions VS scs

Although there are pretty good session managers in the Go ecosystem such as alexedwards/scs, golangcollege/session and gorilla/sessions, we won't use any but using this great guide, we'll write our own. This is to keep our project's dependence on external packages at the barest minimum.

Templates: Go's template/html will work perfectly fine for you. Sessions: https://github.com/gorilla/sessions

gorilla/sessions to manage user sessions.

If you want to persist some form of context between requests you can store it in session data via a cookie that can be pulled/leveraged in the second handler, ex: https://github.com/gorilla/sessions. If you try to implement it yourself consider security aspects like that a user could modify if unsigned, etc. You can also store data server side and just issue a token in a cookie corresponding to a server side session. Hope that helps.

Good ol’ sessions. An example being https://github.com/gorilla/sessions

Although there are pretty good session managers in the Go ecosystem such as alexedwards/scs, golangcollege/session and gorilla/sessions, we won't use any but using this great guide, we'll write our own. This is to keep our project's dependence on external packages at the barest minimum.

github.com/alexedwards/scs is quite pleasant to work with.

This one works ok: https://github.com/alexedwards/scs

I'm a big fan of Alex Edwards' book "Let's Go", and he uses his own Sessions library: https://github.com/alexedwards/scs which you can find in the Authentication section of Awesome Go. So that's a great source as well.

Server side sessions using alexedwards/scs.

Unfortunately I haven't written a cookie/session based auth flow in Golang before so can't recommend any libraries. A quick google led me to https://github.com/alexedwards/scs which may or may not be helpful.