This tool uses a file at $HOME/.juliahub to store credentials.
The reasons for that are:
- do not specify the selected server again and again
- follow the paradigm of
npm, git, aws and other cli tools
- "own" the credentials; i.e. not have them rewritten by a julia process running in the background
Having said that, jh run does copy these credentials to the well known location, while it also sets the JULIA_PKG_SERVER and JULIA_PKG_USE_CLI_GIT in the child process' so it will then use them.
Let's discuss improvements to this approach (i.e. remember the server in ~/.juliahub, but mkdir -p and store the credentials themselves in the well known location, or something similar)
This tool uses a file at
$HOME/.juliahubto store credentials.The reasons for that are:
npm,git,awsand other cli toolsHaving said that,
jh rundoes copy these credentials to the well known location, while it also sets theJULIA_PKG_SERVERandJULIA_PKG_USE_CLI_GITin the child process' so it will then use them.Let's discuss improvements to this approach (i.e. remember the server in
~/.juliahub, butmkdir -pand store the credentials themselves in the well known location, or something similar)