History

Bill Thorp f65a1e8c1c uplink: use output formats for 'uplink access register' instead of writing to AWS file The current uplink access register method has the ability to write to AWS credential files. This is caused issues with repeat usage in recent AWS CLI code, and there was concern that it was an unstable solution. This version instead specifies various output formats "env" and "aws". "env" formats the text so that it can be used with 'export'. "Aws" generates "aws configure" commands to persist the credentials to the AWS credential files as the previous version could. Example usages: Setting ephemeral evironment variables in bash: export $(uplink access register $(storj-sim network env GATEWAY_0_ACCESS) --auth-service http://localhost:8000 --format env) Setting persistant configs via AWS CLI in bash: source <(uplink access register $(storj-sim network env GATEWAY_0_ACCESS) --auth-service http://localhost:8000 --format aws --aws-profile storjsim) Change-Id: I5d78d6462a3537780af3717a298bb2bebf9c2799		2020-12-30 13:34:01 +00:00
..
cmd	uplink: use output formats for 'uplink access register' instead of writing to AWS file	2020-12-30 13:34:01 +00:00
Dockerfile	cmd: ensure proper arch is used for docker container	2020-12-20 09:26:23 +02:00
entrypoint	Adding additional required values for satellite configuration (#1036 )	2019-01-11 22:47:18 -05:00
main.go	private/version: minimal fix for tag-release.sh	2020-04-01 13:46:45 +00:00
README.md	remove identity setup from uplink instructions (#2761 )	2019-08-12 15:40:16 +02:00

README.md

Uplink

Documentation for developing and building the uplink service.

Usage:

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