Live data from Hacker News

Show HN: Caffeine – Minimum viable back end for prototyping

github.com

81–83 of 83 posts

Re: Show HN: Caffeine – Minimum viable back end for prototyping

#81
post #60

Earlier quoted context omitted.

Pretty sure this is meant for prototyping and maybe demoing in controlled environments. As soon as you involve auth, things get boring and annoying.

Honestly, anything simple. It could be as brain-dead simple as passing a password on the command-line, and then requiring the password as a header.

As much as I hate saying it even a simple token in a url parameter might be ok for a prototype.

Re: Show HN: Caffeine – Minimum viable back end for prototyping

#83
post #61

Earlier quoted context omitted.

JWT is crazy annoying compared to "pass an API key" in the header.

> JWT is crazy annoying compared to "pass an API key" in the header. An API key and a JSON WEB TOKEN have a completely different purpose. API keys don't solve authorization. A single JWT provider can authorize many different servers. Furthermore Go already have several good JWT libraries.

For demo application, there maybe only one user
Post reply on HN