69cf6caa62
Uplink CLI was returning an error when the `--config-dir` flag was used with interactive `setup` command because the directory used for storing the encryption key file was the default configuration directory rather than the value set in the flag. This changes make the setup process to use the same directory, than the one informed by the `--config-dir` flag value, for storing encryption key file. On the other hand, the default value for the encryption key file path which was set with the purpose of showing it in the help message has been removed because the cfgstruct doesn't show it unless that the flag is set to the Cobra root CMD, so it was useless. Also show the absolute path where the encryption key file has been saved when the interactive setup command ends satisfactorily as it's equally done with the configuration file. |
||
|---|---|---|
| .. | ||
| cmd | ||
| Dockerfile | ||
| entrypoint | ||
| main.go | ||
| README.md | ||
Uplink
Documentation for developing and building the uplink service.
Usage:
First make an identity:
go install storj.io/storj/cmd/identity
identity create uplink
Then setup the uplink:
go install storj.io/storj/cmd/uplink
uplink setup
You can edit :~/.local/share/storj/uplink/config.yaml to your liking. Then run it!
uplink ls