issue on mac OS

[tgrecojs]

I'm currently setting up my machine (Mac OS) to make use of the CLI booster. Since ZSH is the default terminal for mac, . akash.source doesn't work as expected. Instead, you get the following result where few keys are listed - one of which is the key i wish to make default - and then more keys come afterwards.

Mac OS still comes with bash installed. Users just need to execute bash and afterwards the initialization process runs properly. That said, the initialization process isn't perfect. There are some areas that would benefit from some attention, so I was thinking that this issue could also serve as a tracker for such improvements.

The majority of these issues are likely to be identified as I work to make the akash documentation more user-friendly. For now, I'm going to kick things off with the items listed below. Note: unless otherwise mentioned, then ordering does not matter.

Improvements

• [x] specify that user must use bash #2
• [ ] set PS1, PS2 properly
• [ ] script initialization - load all key names before prompting user to select on.
• [ ] change behaviors so that Mac OS users do not need to re-enter password each step of the way.

[andy108369]

Thanks for filling the issue @tgrecojs I don't have macOS, unfortunately, so I can't test much.

But yeah, initialization process should be improved indeed. Currently it just scans all three keyring backends "os", "file" and "test" to then use the one which has more keys (assuming that's the primary keystore). The first two (os, file) are typically passhrase-protected, hence it wants you to enter a correct passphrase. You could also export the "AKASH_KEYRING_BACKEND" to set it to either, the one you know is the right one or rather just use "test" keyring backend which never asks for the passphrase. But then you would want to migrate your keys there.