...
| Code Block |
|---|
portal:> remote portal [ not connected ] * public [ not connected ] aws [ not connected to: https://data.pawsey.org.au:443 public not connected to: https://] |
You can query the configuration of a particular remote as follows:
| Code Block |
|---|
portal:/>remote portal --info name = portal type = mflux protocol = https server = data.pawsey.org.au:443 awsport = 443 domain not connected to: 'ap-southeast-2' pawsey0002 not connected to: https://acacia.pawsey.org.au= ivec |
New remotes can be added for a an additional Mediaflux server (such as similar to the default portal and public above) or for an S3 resourcesresource. For further information, see: pshell and S3 remotes.
...
Authenticate to a remote using the appropriate credentials. In the case of the data portal it will be your Pawsey credentials. In the case of an S3 resource it will be your key and secret pair. If the login was successful, the connection status of the remote will be updated.
| Code Block |
|---|
portal:>login Username: sean Password: portal:>/>remote remote portal authenticated to: https://data.pawsey.org.au/aterm as user=ivec:sean public not connected to: https://data.pawsey.org.au:443[ authenticated ] * public [ not connected ] aws [ not connected ] |
You can now navigate (cd, ls) and transfer files (put, get) between your local filesystem and your remote storage resource.
...
To see an overview of the available commands, type "help" at the prompt. You can also type "help <command>" to obtain specific help on the named command.
| Code Block |
|---|
portal:/>help DocumentedStandard commands (type help <topic>): ======================================== cd get info login ls publish quit rmdir delegate help lcd logout mkdir put remote unpublish exit import lls lpwd processes pwd rm whoami portal:/>help get info login Returnls informationpublish forquit armdir remote file orSpecialised folder Usage: info <filename/folder>commands ==================== delegate lifecycle policy |