3 ms·

What about templating, middlewares, security, authentication, authorization? Do I need to glue this from custom libraries to the web server myself every time I

• kevinburke 10y ago
  - there's a templating example in the project - there are middleware examples in the blog post and in the project - depends on what you mean by "sucurity". there's an example of secure cookie encryption in the blog post and the project - depends on what sort of authentication or authorization you need. If you just need basic auth you can try https://godoc.org/github.com/kevinburke/handlers#BasicAuth https://godoc.org/github.com/kevinburke/handlers#BasicAuth
  • Gonzih 10y ago
    - ok, i did not look at example, sorry - for logging, but thats not enough - thanks for pointing out typo in an interesting way, yeah but blogpost just mentions custom library that should be glued to your webserver - custom library again glued to the server on every project I would go for new projects with something different than go. Like scala. Go is great for rest apis, but once your app becomes more "complete" in terms of requirements go becomes more and more painful in my experience.
    • kevinburke 10y ago
      > I would go for new projects with something different than go. You should probably write your own article then.