uuid VS certmagic

https://github.com/gofrs/uuid upto v5

I use Google's UUID package a lot. But every time I refer to it in a new package, the language server picks up https://github.com/gofrs/uuid instead of https://github.com/google/uuid and then complains that the gofrs package isn't in go.mod. I assume because it's the first alphabetically (though this seems like a huge supply chain security loophole).

What makes this different than https://github.com/gofrs/uuid ?

Something to note is that all of this is still open source. Theoretically, someone can decide to fork SQLBoiler and add all the missing things, or send in a PR. A good example is that the current most popular uuid package. gofrs/uuid was forked from an unmaintained previously popular package.

You could also look at github.com/gofrs/uuid which includes support for v6 and v7 from the latest draft UUID spec. Personally I think the API for this library is nicer since the google one makes it difficult to tell what kind of UUID you are generating.

Postgres has native UUID support so don't use VARCHAR(36). Look at https://github.com/gofrs/uuid library, among others, to create uuid.

If you're using this library and are unsure what to do, a few of us maintain a fork of this library that has fixed these issues (and others): https://github.com/gofrs/uuid

Now, I serve TLS directly from the application and was able to make it all work with Certmagic.

For deployment, you may not need a reverse proxy with Nginx or the likes. Certmagic will make HTTPS a breeze. Also makes it possible to handle multi-tenant SaaS domains SSL provisioning. While not the easiest, it was much easier than trying to do it at the reverse proxy and cheaper than doing it with Cloudflare's SaaS service.

If you don't want to move certificate management to a different service, use CertMagic in your app.

With certmagic its done completly automatic using letsencrypt: https://github.com/caddyserver/certmagic

The project is also a boon for devs. The certmagic library0 makes it trivial to add Let's Encrypt support to any Golang web server code.

Because Lego maintainers wouldn't budge when Caddy needed changes made to increase ACME reliability. Matt wrote his own implementation https://github.com/mholt/acmez and started using that in Caddy soon after. There's a deeper explanation here: https://github.com/caddyserver/certmagic/issues/71

That said, I would use https://github.com/caddyserver/certmagic to manage you SSL certs.

I terminate SSL in GO (less moving parts to manage), and use https://github.com/caddyserver/certmagic to provision and renew my certs.