...
| Code Block |
|---|
portal:> remote portal [ authenticatednot connected ] * public [ not connected ] aws [ not connected ] |
...
New remotes can be added for an additional Mediaflux server (similar to the default portal and public) or for an S3 resource. An example of adding an acacia project is shown below:
| Code Block |
|---|
portal:/>remote pawsey0961 s3 https://projects.pawsey.org.au
portal:> remote
portal [ authenticated ] *
public [ not connected ]
pawsey0961 [ login required ]
portal:/>remote pawsey0961
pawsey0961:/>login
Access: abc123
Secret: |
For 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 Documented commands (type help <topic>): =========Standard commands =============================== 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:/>helpget info login Returnls informationpublish forquit armdir remote file orSpecialised folder Usage: info <filename/folder>commands ==================== delegate lifecycle policy |