Pijul doesn’t help you get started. Can’t I try a local repo? It says I need a key.
pijul init pijul add * pijul record -m "import of source"
The message is only
Error: No identity configured yet. Please use `pijul key` to create one
pijul key generate gives
error: The following required arguments were not provided: `<LOGIN>` USAGE: pijul key generate [OPTIONS] `<LOGIN>` For more information try --help
The specific help doesn’t help. It doesn’t say what a
<LOGIN> is. (and it shows the standard flags that aren’t relevant)
USAGE: pijul key generate [OPTIONS] `<LOGIN>` ARGS: `<LOGIN>` FLAGS: -h, --help Print help information -V, --version Print version information OPTIONS: --email `<EMAIL>`
I had to put backticks around the angle bracketed stuff or Nest stripped them out. Maybe it would be better to use other characters in the actual help text, so it’s not a forever battle with HTML tags.
OK, so the
init needs to prompt for that, or there should be a way to have a local repo without a key, or the help text needs to be more explicit (and matching) so that the user knows what’s going on.
Or all of the above. Everyone should not have to ask you what this means. It doesn’t even mention the Nest.
Agreed it’s not super obvious. Keys are a relative new addition to Pijul, and thus lack some still in UX. I’ll take a look at this issue some time later and see what of your suggestions can be implemented.
About the mention of the Nest, I think Pijul should be hosting agnostic. If a company wants to someday host their server on pijul.company.tld mentioning the nest will be confusing.
@joyously It is the same behaviour
git shows when you never have used git. (Although, they have better error messages.) When you never have used git, it would prompt you on the first
git commit that you haven’t specified an author name and e-mail address, yet. That’s what pijul tries to tell you.
You only need to make an identity with
pijul key generate once. After that, pijul won’t complain again.