drduh
simplified guide version
to aid in automation and encourage use, the guide could benefit from being split in two: a simplified (perhaps scripted?) version and the current detailed, in-depth version covering advanced topics.
Hello. I have a couple of ideas how to simplify the guide, I've tested them briefly, and they seem to work together with no issues.
First, I'm not sure scripting would be that helpful, as it makes troubleshooting harder. What if we made a notebook? This would help to avoid a lot of error-prone copypasting. Jupyter is fine, but we could also use emacs, it is easy to install in addition to all other things, and it's shipped with org-mode, which can be used for notebooks and running code blocks. I've tried generating a key in it and it worked great. Although jupyter is what more people are used to.
Second, it would be cool to let users have a trial run in docker, so that they can be prepared to see what's going to happen when they generate keys in a trusted environment. I managed to make a rootless podman container based on debian with a non-root user, in which we can access the token. Unfortunately, this didn't work in docker. This may or may not be an issue, but I prefer to avoid root in containers. I can't decide if having podman as the only option for the trial run is ok. I also tried to install nix in the container and couldn't have access either.
Please let me know if you find these ideas worth developing further, and I'll clean up and share the code I've tested then.
