keygen-go VS pkg

Why would you want to scroll horizontally? Or are you referring to the code samples? It's only a code "sample" (i.e. non-working just to show off the platform), so fingerprint would likely come from something like https://github.com/denisbrodbeck/machineid. Full examples are available in the Go SDK docs [^0].

[^0]: https://github.com/keygen-sh/keygen-go

I run https://keygen.sh by myself. I built it about 7 years ago and started running it on the side. I went full-time on it in 2020 when it got too big to run on the side. As for trends -- the market is a bit slower these days due to the current economic environment. I've noticed smaller businesses have had a tougher time buying (and staying on), while enterprises have had an uptick.

Working on adding “environments” to my business’ API (https://keygen.sh). I’ve gone over 6 years without offering a “sandbox” environment to customers, so I’m excited to finally be working on this one. It’s been quite complex implementatiom-wise, and has touched a lot of surface area, since I want it to support multiple named environments (e.g. staging, dev, one-offs isolated test envs for CI/CD). But it’ll be worth it.

Check out https://github.com/keygen-sh/keygen-go. Has auto-upgrade support for Go apps.

I don't remember the details, and cannot find my notes on vercel/pkg. But looking at https://github.com/vercel/pkg right now I see the project has been deprecated in favour of single-executable-applications

> Standalone CLI — we haven’t worked on a standalone CLI for the new engine yet, but will absolutely have it before the v4.0 release.

This part is the most exciting to me. Given the rest of the release announcement, I'm assuming this means that it'll be built in Rust rather than embed Node. While I'm not a Rust zealot of anything, I'm very partial to not embedding Node. Particularly when it depends on using Vercel's now-abandoned pkg[1] tool.`

[1] https://github.com/vercel/pkg

The npm package called "pkg" seems to be the standard for packaging NodeJS applications

https://www.npmjs.com/package/pkg

Unfortunately you also need to bundle all your code into a single file for it to work, but you can use any bundler (webpack, parcel, etc) you want at least

Nodejs support for "single executable applications" is getting there - this issue below is preventing wider adoption at the moment:

"The single executable application feature currently only supports running a single embedded script using the CommonJS module system."

https://nodejs.org/api/single-executable-applications.html

Should be an awesome game changer for node.js when the feature gets rounded out.

Also check out vercel's `pkg`: https://github.com/vercel/pkg/issues/1291

Yes, you can. Check out pkg for a fun option, which can package up your project and Node.js into a single executable.

Further, you could experiment with the pkg tool that allows you to package up Node JS, your source, and your dependencies into one single executable for easy distribution.

package the app using https://github.com/vercel/pkg and use a smaller base image like alpine, busybox or even scratch (if possible)

Check this thread: https://github.com/vercel/pkg/issues/1685