The working with others section needs proper bootstrapping warnings before getting into Nest. Ahhh I remember now! It was Nest that was also weird as hell. And Discourse.pijul.com.
Ok so the Manual needs to acknowledge that an edited down Getting Setup Before You Record“ section with stuff about
pijul identity new <yourname>
ssh-keygen
sorted out if you’re going to be using the Nest section which is later on.
Literally the guide walks you through things out of order. Like a stack trace this is end first beginning last:
pijul identity
is not even in there and you have to Sherlock Holmes it out when you seepijul key
.pijul key generate
doesn’t exist. It’spijul identity new
. Luckily thepijul help identity
output is actually:–like good. It’s short enough you’re not in a labyrinth of hell. Pijul as it is now is already better than git in this regard.any else weirdnesses? Favorable note: The install into WSL was nice and smooth like something people have down smooth. I appreciated that. I considered getting Nix so I could have the same process on WSL and Mac OS X.
my work has a TLS intercepting proxy so I’m avoiding that crap until I know what I’m doing at home. That thing sucks majorly for all DevOps compiling type processes. Everything is a web client and webclients are browsers that need manual config EACH! And the World Trusted Roots Lists per tool are not centralized because they’re not supposed to be updated by companies internal CAs. Or so community run software libraries seem to think.