aspera-cli 4.12.0 → 4.13.0

data/README.md

@@ -1,13 +1,12 @@
 # Command Line Interface for IBM Aspera products
 <!-- markdownlint-disable MD033 MD003 MD053 -->
-<!-- cSpell:ignore devkit zcvf zxvf noded secondfile filesize sedemo eudemo webmail csum eascp loglevel cronfile magick keepalive inotify eastus bluemix trev sshfp struct genkey passout ibmaspera unpermitted -->
-<!-- cSpell:ignoreRegExp /-P[a-z]+/g -->
-<!-- cSpell:ignoreRegExp /my[a-z]+/g -->
+<!-- cSpell:ignore devkit zcvf zxvf noded secondfile filesize sedemo eudemo webmail csum eascp loglevel cronfile magick keepalive inotify eastus bluemix trev sshfp struct genkey passout ibmaspera unpermitted schtasks taskschd -->
+
 [comment1]: # (Do not edit this README.md, edit docs/README.erb.md, for details, read docs/README.md)
 
 ##
 
-Version : 4.12.0
+Version : 4.13.0
 
 Laurent/2016-2023
 
@@ -19,9 +18,9 @@ Ruby Gem: [https://rubygems.org/gems/aspera-cli](https://rubygems.org/gems/asper
 
 Ruby Doc: [https://www.rubydoc.info/gems/aspera-cli](https://www.rubydoc.info/gems/aspera-cli)
 
-Minimum required Ruby version: >= 2.4.
+Minimum required Ruby version: >= 2.6.
 
-> **Deprecation notice**: the minimum Ruby version will be 2.7 in a future version.
+> **Deprecation notice**: the minimum Ruby version will be 3.0 in a future version.
 
 [Aspera APIs on IBM developer](https://developer.ibm.com/?size=30&q=aspera&DWContentType[0]=APIs&sort=title_asc)
 [Link 2](https://developer.ibm.com/apis/catalog/?search=aspera)
@@ -58,7 +57,7 @@ So it is designed for:
 If the need is to perform operations programmatically in languages such as: C, Go, Python, nodejs, ... then it is better to directly use [Aspera APIs](https://ibm.biz/aspera_api)
 
 - Product APIs (REST) : e.g. AoC, Faspex, node
-- Transfer SDK : with gRPC interface and language stubs (C, C++, Python, .NET/C#, java, ruby, etc...)
+- Transfer SDK : with gRPC interface and language stubs (C, C++, Python, .NET/C#, java, Ruby, etc...)
 
 Using APIs (application REST API and transfer SDK) will prove to be easier to develop and maintain.
 
@@ -93,7 +92,7 @@ ascli --version
 ```
 
 ```bash
-4.12.0
+4.13.0
 ```
 
 ### First use
@@ -104,8 +103,6 @@ If you want to test with Aspera on Cloud, jump to section: [Wizard](#aocwizard)
 
 To test with Aspera demo transfer server, setup the environment and then test:
 
-<!-- spellchecker: disable -->
-
 ```bash
 ascli config initdemo
 ```
@@ -115,18 +112,16 @@ ascli server browse /
 ```
 
 ```output
-:............:...........:......:........:...........................:.......................:
-:   zmode    :   zuid    : zgid :  size  :           mtime           :         name          :
-:............:...........:......:........:...........................:.......................:
-: dr-xr-xr-x : asperaweb : fasp : 4096   : 2014-04-10 19:44:05 +0200 : aspera-test-dir-tiny  :
-: drwxr-xr-x : asperaweb : fasp : 176128 : 2018-03-15 12:20:10 +0100 : Upload                :
-: dr-xr-xr-x : asperaweb : fasp : 4096   : 2015-04-01 00:37:22 +0200 : aspera-test-dir-small :
-: dr-xr-xr-x : asperaweb : fasp : 4096   : 2018-05-04 14:26:55 +0200 : aspera-test-dir-large :
-:............:...........:......:........:...........................:.......................:
++------------+-----------+-----------+-------+---------------------------+-----------------------+
+| zmode      | zuid      | zgid      | size  | mtime                     | name                  |
++------------+-----------+-----------+-------+---------------------------+-----------------------+
+| drwxr-xr-x | asperaweb | asperaweb | 90112 | 2023-04-05 15:31:21 +0200 | Upload                |
+| dr-xr-xr-x | asperaweb | asperaweb | 4096  | 2022-10-27 16:08:16 +0200 | aspera-test-dir-large |
+| dr-xr-xr-x | asperaweb | asperaweb | 4096  | 2022-10-27 16:08:17 +0200 | aspera-test-dir-small |
+| dr-xr-xr-x | asperaweb | asperaweb | 4096  | 2022-10-27 16:08:17 +0200 | aspera-test-dir-tiny  |
++------------+-----------+-----------+-------+---------------------------+-----------------------+
 ```
 
-<!-- spellchecker: enable -->
-
 If you want to use `ascli` with another server, and in order to make further calls more convenient, it is advised to define a [option preset](#lprt) for the server's authentication options. The following example will:
 
 - create a [option preset](#lprt)
@@ -155,17 +150,17 @@ ascli server browse /aspera-test-dir-large
 ```
 
 ```output
-:............:...........:......:..............:...........................:............................:
-:   zmode    :   zuid    : zgid :     size     :           mtime           :            name            :
-:............:...........:......:..............:...........................:............................:
-: -rw-r--r-- : asperaweb : fasp : 209715200    : 2014-04-10 19:49:27 +0200 : 200MB                      :
-: -rw-r--r-- : asperaweb : fasp : 524288000    : 2014-04-10 19:44:15 +0200 : 500MB                      :
-: -rw-r--r-- : asperaweb : fasp : 5368709120   : 2014-04-10 19:45:52 +0200 : 5GB                        :
-: -rw-r--r-- : asperaweb : fasp : 500000000000 : 2017-06-14 20:09:57 +0200 : 500GB                      :
-: -rw-r--r-- : asperaweb : fasp : 1048576000   : 2014-04-10 19:49:23 +0200 : 1GB                        :
-: -rw-r--r-- : asperaweb : fasp : 104857600    : 2014-04-10 19:49:29 +0200 : 100MB                      :
-: -rw-r--r-- : asperaweb : fasp : 10737418240  : 2014-04-10 19:49:04 +0200 : 10GB                       :
-:............:...........:......:..............:...........................:............................:
++------------+-----------+-----------+--------------+---------------------------+-------+
+| zmode      | zuid      | zgid      | size         | mtime                     | name  |
++------------+-----------+-----------+--------------+---------------------------+-------+
+| -r-xr-x--- | asperaweb | asperaweb | 104857600    | 2022-10-27 16:06:38 +0200 | 100MB |
+| -r-xr-x--- | asperaweb | asperaweb | 10737418240  | 2022-10-27 16:08:12 +0200 | 10GB  |
+| -r-xr-x--- | asperaweb | asperaweb | 500000000000 | 2022-10-27 16:06:26 +0200 | 500GB |
+| -r-xr-x--- | asperaweb | asperaweb | 524288000    | 2022-10-27 14:53:00 +0200 | 500MB |
+| -r-xr-x--- | asperaweb | asperaweb | 1048576000   | 2022-10-27 16:06:37 +0200 | 1GB   |
+| -r-xr-x--- | asperaweb | asperaweb | 5368709120   | 2022-10-27 14:53:47 +0200 | 5GB   |
+| -r-xr-x--- | asperaweb | asperaweb | 209715200    | 2022-10-27 14:52:56 +0200 | 200MB |
++------------+-----------+-----------+--------------+---------------------------+-------+
 ```
 
 ```bash
@@ -185,7 +180,7 @@ Then, follow the section relative to the product you want to interact with ( Asp
 
 ## <a id="installation"></a>Installation
 
-It is possible to install *either* directly on the host operating system (Linux, Windows, macOS) or as a docker container.
+It is possible to install **either** directly on the host operating system (Linux, macOS, Windows) or as a container (`docker`).
 
 The direct installation is recommended and consists in installing:
 
@@ -193,9 +188,9 @@ The direct installation is recommended and consists in installing:
 - [aspera-cli](#the_gem)
 - [Aspera SDK (`ascp`)](#fasp_prot)
 
-Ruby version: >= 2.4.
+Ruby version: >= 2.6.
 
-> **Deprecation notice**: the minimum Ruby version will be 2.7 in a future version.
+> **Deprecation notice**: the minimum Ruby version will be 3.0 in a future version.
 
 The following sections provide information on the various installation methods.
 
@@ -205,16 +200,18 @@ An internet connection is required for the installation. If you don't have inter
 
 The image is: [martinlaurent/ascli](https://hub.docker.com/r/martinlaurent/ascli).
 The container contains: Ruby, `ascli` and the Aspera Transfer SDK.
-To use the container, ensure that you have `docker` (or `podman`) installed.
+To use the container, ensure that you have `podman` (or `docker`) installed.
 
 ```bash
-docker --version
+podman --version
 ```
 
+#### Container quick start
+
 **Wanna start quickly ?** With an interactive shell ? Execute this:
 
 ```bash
-docker run --tty --interactive --entrypoint bash martinlaurent/ascli:latest
+podman run --tty --interactive --entrypoint bash martinlaurent/ascli:latest
 ```
 
 Then, execute individual `ascli` commands such as:
@@ -232,18 +229,22 @@ That is simple, but there are limitations:
 - Any generated file in the container will be lost on container (shell) exit. Including configuration files and downloaded files.
 - No possibility to upload files located on the host system
 
+#### Details on the container
+
 The container image is built from this [Dockerfile](Dockerfile): the entry point is `ascli` and the default command is `help`.
 
+If you want to run the image with a shell, execute with option: `--entrypoint bash`, and give argument `-l` (bash login to override the `help` default argument)
+
 The container can also be execute for individual commands like this: (add `ascli` commands and options at the end of the command line, e.g. `-v` to display the version)
 
 ```bash
-docker run --rm --tty --interactive martinlaurent/ascli:latest
+podman run --rm --tty --interactive martinlaurent/ascli:latest
 ```
 
 For more convenience, you may define a shell alias:
 
 ```bash
-alias ascli='docker run --rm --tty --interactive martinlaurent/ascli:latest'
+alias ascli='podman run --rm --tty --interactive martinlaurent/ascli:latest'
 ```
 
 Then, you can execute the container like a local command:
@@ -253,7 +254,7 @@ ascli -v
 ```
 
 ```text
-4.12.0
+4.13.0
 ```
 
 In order to keep persistency of configuration on the host,
@@ -265,7 +266,7 @@ Add options:
 --user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli
 ```
 
-> **Note:** if you are using a `podman machine`, e.g. on Macos , make sure that the folder is also shared between the VM and the host, so that sharing is: container &rarr; VM &rarr; Host: `podman machine init ... --volume="/Users:/Users"`
+> **Note:** if you are using a `podman machine`, e.g. on macOS , make sure that the folder is also shared between the VM and the host, so that sharing is: container &rarr; VM &rarr; Host: `podman machine init ... --volume="/Users:/Users"`
 
 As shown in the quick start, if you prefer to keep a running container with a shell and `ascli` available,
 you can change the entry point, add option:
@@ -286,7 +287,7 @@ In this case you need also to mount the shared transfer folder:
 And if you want all the above, simply use all the options:
 
 ```bash
-alias asclish="docker run --rm --tty --interactive --user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli --volume $HOME/xferdir:/xferfiles --entrypoint bash martinlaurent/ascli:latest"
+alias asclish="podman run --rm --tty --interactive --user root --env ASCLI_HOME=/home/cliuser/.aspera/ascli --volume $HOME/.aspera/ascli:/home/cliuser/.aspera/ascli --volume $HOME/xferdir:/xferfiles --entrypoint bash martinlaurent/ascli:latest"
 ```
 
 ```bash
@@ -297,6 +298,8 @@ mkdir -p $HOME/.aspera/ascli
 asclish
 ```
 
+#### Sample container script
+
 A convenience sample script is also provided: download the script [`dascli`](../examples/dascli) from [the GIT repo](https://raw.githubusercontent.com/IBM/aspera-cli/main/examples/dascli) :
 
 > **Note:** If you have installed `ascli`, the script `dascli` can also be found: `cp $(ascli conf gem path)/../examples/dascli ascli`
@@ -306,7 +309,7 @@ Some environment variables can be set for this script to adapt its behavior:
 | env var      | description                        | default                  | example                  |
 |--------------|------------------------------------|--------------------------|--------------------------|
 | ASCLI_HOME | configuration folder (persistency) | `$HOME/.aspera/ascli` | `$HOME/.ascliconfig`     |
-| docker_args  | additional options to `docker`     | &lt;empty&gt;            | `--volume /Users:/Users` |
+| docker_args  | additional options to `podman`     | &lt;empty&gt;            | `--volume /Users:/Users` |
 | image        | container image name               | martinlaurent/ascli      |                          |
 | version      | container image version            | latest                   | `4.8.0.pre`              |
 
@@ -333,22 +336,44 @@ echo 'Local file to transfer' > $xferdir/samplefile.txt
 ```
 
 > **Note:** The local file (`samplefile.txt`) is specified relative to storage view from container (`/xferfiles`) mapped to the host folder `$HOME/xferdir`
+>
+> **Note:** Do not use too many volumes, as the AUFS limits the number.
+
+#### Offline installation of the container
+
+- First create the image archive:
+
+```bash
+podman pull martinlaurent/ascli
+podman save martinlaurent/ascli|gzip>ascli_image_latest.tar.gz
+```
+
+- Then, on air-gapped system:
+
+```bash
+podman load -i ascli_image_latest.tar.gz
+```
 
 ### <a id="ruby"></a>Ruby
 
 Use this method to install on the native host.
 
-A ruby interpreter is required to run the tool or to use the gem and tool.
+A Ruby interpreter is required to run the tool or to use the gem and tool.
 
-Required Ruby version: >= 2.4.
+Required Ruby version: >= 2.6.
 
-> **Deprecation notice**: the minimum Ruby version will be 2.7 in a future version.
+> **Deprecation notice**: the minimum Ruby version will be 3.0 in a future version.
 
 *Ruby can be installed using any method* : rpm, yum, dnf, rvm, brew, windows installer, ... .
 
-Refer to the following sections for a proposed method for specific operating systems.
+In priority, refer to the official Ruby documentation:
 
-The recommended installation method is `rvm` for systems with "bash-like" shell (Linux, macOS, Windows with cygwin, etc...).
+- [Download Ruby](https://www.ruby-lang.org/en/downloads/)
+- [Installation Guide](https://www.ruby-lang.org/en/documentation/installation/)
+
+Else, refer to the following sections for a proposed method for specific operating systems.
+
+The recommended installation method is `rvm` for Unix-like systems (Linux, AIX, macOS, Windows with cygwin, etc...).
 If the generic install is not suitable (e.g. Windows, no cygwin), you can use one of OS-specific install method.
 If you have a simpler better way to install Ruby : use it !
 
@@ -356,7 +381,7 @@ If you have a simpler better way to install Ruby : use it !
 
 Use this method which provides more flexibility.
 
-Install "rvm": follow [https://rvm.io/](https://rvm.io/) :
+Install `rvm`: follow [https://rvm.io/](https://rvm.io/) :
 
 Execute the shell/curl command. As regular user, it install in the user's home: `~/.rvm` .
 
@@ -372,7 +397,7 @@ If you keep the same terminal (not needed if re-login):
 source ~/.rvm/scripts/rvm
 ```
 
-It is advised to get one of the pre-compiled ruby version, you can list with:
+It is advised to get one of the pre-compiled Ruby version, you can list with:
 
 ```bash
 rvm list --remote
@@ -381,10 +406,10 @@ rvm list --remote
 Install the chosen pre-compiled Ruby version:
 
 ```bash
-rvm install 2.7.2 --binary
+rvm install 3.2.2
 ```
 
-Ruby is now installed for the user, go on to Gem installation.
+Ruby is now installed for the user, go to [Gem installation](#the_gem).
 
 #### Generic: RVM: global installation (as root)
 
@@ -399,7 +424,7 @@ curl -sSL https://get.rvm.io | bash -s -- --path /usr/local
 
 As root, make sure this will not collide with other application using Ruby (e.g. Faspex).
 If so, one can rename the login script: `mv /etc/profile.d/rvm.sh /etc/profile.d/rvm.sh.ok`.
-To activate ruby (and ascli) later, source it:
+To activate Ruby (and ascli) later, source it:
 
 ```bash
 source /etc/profile.d/rvm.sh.ok
@@ -434,7 +459,7 @@ brew install ruby
 
 #### Linux: package
 
-If your Linux distribution provides a standard ruby package, you can use it provided that the version is compatible (check at beginning of section).
+If your Linux distribution provides a standard Ruby package, you can use it provided that the version is compatible (check at beginning of section).
 
 Example: RHEL 8 and 9: basic installation
 
@@ -462,7 +487,7 @@ yum install -y ruby ruby-devel rubygems ruby-json
 apt install -y ruby ruby-dev rubygems ruby-json
 ```
 
-One can cleanup the whole yum-installed ruby environment like this to uninstall:
+One can cleanup the whole yum-installed Ruby environment like this to uninstall:
 
 ```bash
 gem uninstall $(ls $(gem env gemdir)/gems/|sed -e 's/-[^-]*$//'|sort -u)
@@ -475,7 +500,7 @@ For example for AIX, one can look at:
 
 <https://www.ibm.com/support/pages/aix-toolbox-open-source-software-downloads-alpha#R>
 
-If your Unix does not provide a pre-built ruby, you can get it using one of those
+If your Unix does not provide a pre-built Ruby, you can get it using one of those
 [methods](https://www.ruby-lang.org/en/documentation/installation/).
 
 For instance to build from source, and install in `/opt/ruby` :
@@ -502,7 +527,7 @@ If you already have a Java JVM on your system (`java`), it is possible to use `j
 
 <https://www.jruby.org/download>
 
-> **Note:** Using jruby the startup time is longer than the native ruby, but the transfer speed is not impacted (executed by `ascp` binary).
+> **Note:** Using jruby the startup time is longer than the native Ruby, but the transfer speed is not impacted (executed by `ascp` binary).
 
 ### <a id="the_gem"></a>`aspera-cli` gem
 
@@ -556,7 +581,6 @@ If the embedded method is not used, the following packages are also suitable:
 
 - IBM Aspera Connect Client (Free)
 - IBM Aspera Desktop Client (Free)
-- IBM Aspera CLI (Free)
 - IBM Aspera High Speed Transfer Server (Licensed)
 - IBM Aspera High Speed Transfer EndPoint (Licensed)
 
@@ -670,9 +694,9 @@ Moreover all `ascp` options are supported either through transfer spec parameter
 `ascli` is typically executed in a shell, either interactively or in a script.
 `ascli` receives its arguments from this shell (through Operating System).
 
-#### Shell parsing for Linux, Unix, Macos
+#### Shell parsing for Unix-like systems: Linux, macOS, AIX
 
-On Linux and Unix environments, this is typically a POSIX shell (bash, zsh, ksh, sh).
+On Unix-like environments, this is typically a POSIX shell (bash, zsh, ksh, sh).
 In this environment the shell parses the command line, possibly replacing variables, etc...
 see [bash shell operation](https://www.gnu.org/software/bash/manual/bash.html#Shell-Operation).
 Then it builds a list of arguments and then `ascli` (Ruby) is executed.
@@ -690,7 +714,7 @@ It's up to the program to parse arguments. Ruby follows the Microsoft C/C++ para
 
 #### Extended Values (JSON, Ruby, ...)
 
-Some of the CLI parameters are expected to be [Extended Values](#extended), i.e. not a simple strings, but a complex structure (Hash, Array).
+Some of the `ascli` parameters are expected to be [Extended Values](#extended), i.e. not a simple strings, but a complex structure (Hash, Array).
 Typically, the `@json:` modifier is used, it expects a JSON string. JSON itself has some special syntax: for example `"` is used to denote strings.
 
 #### Testing Extended Values
@@ -841,7 +865,7 @@ ascli conf echo @env:MYTITLE --format=text
 Test " ' & \
 ```
 
-If the value to be used is in a more complex structure, then the `@ruby:` modifier can be used: it allows any ruby code in expression, including reading from file or env var. In those cases, there is no character to protect because values are not parsed by the shell, or JSON or even Ruby.
+If the value to be used is in a more complex structure, then the `@ruby:` modifier can be used: it allows any Ruby code in expression, including reading from file or env var. In those cases, there is no character to protect because values are not parsed by the shell, or JSON or even Ruby.
 
 ```bash
 ascli conf echo @ruby:"{'title'=>File.read('title.txt')}" --format=json
@@ -972,12 +996,12 @@ ascli aoc admin res user list --fields=name,email,ats_admin --query=@json:'{"sor
 ```
 
 ```output
-:...............................:..................................:...........:
-:             name              :              email               : ats_admin :
-:...............................:..................................:...........:
-: John Curtis                   : john@example.com                 : true      :
-: Laurent Martin                : laurent@example.com              : true      :
-:...............................:..................................:...........:
++-------------------------------+----------------------------------+-----------+
+|             name              |              email               | ats_admin |
++-------------------------------+----------------------------------+-----------+
+| John Curtis                   | john@example.com                 | true      |
+| Laurent Martin                | laurent@example.com              | true      |
++-------------------------------+----------------------------------+-----------+
 ```
 
 > **Note:** `select` filters selected elements from the result of API calls, while the `query` parameters gives filtering parameters to the API when listing elements.
@@ -1012,38 +1036,38 @@ By default, a table output will display one line per entry, and columns for each
 
 ### <a id="extended"></a>Extended Value Syntax
 
-Usually, values of options and arguments are specified by a simple string. But sometime it is convenient to read a value from a file, or decode it, or have a value more complex than a string (e.g. Hash table).
+Some options and arguments are specified by a simple string.
+But sometime it is convenient to read a value from a file, or decode it, or have a value more complex than a string (e.g. Hash table).
 
 The extended value syntax is:
 
 ```bash
-<0 or more decoders><0 or 1 reader><nothing or some text value>
+<0 or more decoders><nothing or some text value>
 ```
 
-The difference between reader and decoder is order and cardinality.
-Both act like a function of value on right hand side.
-Decoders are at the beginning of the value, followed by a single optional reader, followed by the optional value.
-
-The following "readers" are supported (returns value in []):
+Decoders act like a function of value on right hand side.
+Decoders are recognized by the prefix: `@` and suffix `:`
 
-- @val:VALUE   : [String] prevent further special prefix processing, e.g. `--username=@val:laurent` sets the option `username` to value `laurent`.
-- @file:PATH   : [String] read value from a URL, e.g. `--fpac=@uri:http://serv/f.pac`
-- @uri:URL     : [String] read value from a file (prefix `~/` is replaced with the users home folder), e.g. `--key=@file:~/.ssh/mykey`
-- @path:PATH   : [String] performs path expansion (prefix `~/` is replaced with the users home folder), e.g. `--config-file=@path:~/sample_config.yml`
-- @env:ENVVAR  : [String] read from a named env var, e.g.--password=@env:MYPASSVAR
-- @stdin:      : [String] read from stdin (no value on right)
-- @preset:NAME : [Hash] get whole option preset value by name. Sub-values can also be used using `.` as separator. e.g. `foo.bar` is `conf[foo][bar]`
+The following decoders are supported:
 
-In addition it is possible to decode a value, using one or multiple decoders :
-
-- @base64: [String] decode a base64 encoded string
-- @json: [any] decode JSON values (convenient to provide complex structures)
-- @zlib: [String] un-compress data
-- @ruby: [any] execute ruby code
-- @csvt: [Array] decode a titled CSV value
-- @lines: [Array] split a string in multiple lines and return an array
-- @list: [Array] split a string in multiple items taking first character as separator and return an array
-- @incps: [Hash] include values of presets specified by key `incps` in input hash
+| decoder | parameter | returns | description |
+|---------|-----------|---------|-------------|
+| base64  | String    | String  | decode a base64 encoded string
+| csvt    | String    | Array   | decode a titled CSV value
+| env     | String    | String  | read from a named env var name, e.g.--password=@env:MYPASSVAR
+| file    | String    | String  | read value from specified file (prefix `~/` is replaced with the users home folder), e.g. `--key=@file:~/.ssh/mykey` |
+| incps   | Hash      | Hash    | include values of presets specified by key `incps` in input hash
+| json    | String    | any     | decode JSON values (convenient to provide complex structures)
+| lines   | String    | Array   | split a string in multiple lines and return an array
+| list    | String    | Array   | split a string in multiple items taking first character as separator and return an array
+| path    | String    | String  | performs path expansion on specified path (prefix `~/` is replaced with the users home folder), e.g. `--config-file=@path:~/sample_config.yml` |
+| preset  | String    | Hash    | get whole option preset value by name. Sub-values can also be used using `.` as separator. e.g. `foo.bar` is `conf[foo][bar]`
+| ruby    | String    | any     | execute specified Ruby code
+| secret  | None      | String  | Ask password interactively (hides input)
+| stdin   | None      | String  | read from stdin (no value on right)
+| uri     | String    | String  | read value from specified URL, e.g. `--fpac=@uri:http://serv/f.pac` |
+| val     | String    | String  | prevent decoders on the right to be decoded. e.g. `--key=@val:@file:foo` sets the option `key` to value `@file:foo`. |
+| zlib    | String    | String  | un-compress data
 
 To display the result of an extended value, use the `config echo` command.
 
@@ -1076,12 +1100,12 @@ ascli config echo @csvt:@file:test.csv
 ```
 
 ```output
-:......:.....................:
-: name :        email        :
-:......:.....................:
-: lolo : laurent@example.com :
-: toto : titi@tutu.tata      :
-:......:.....................:
++------+---------------------+
+| name |        email        |
++------+---------------------+
+| lolo | laurent@example.com |
+| toto | titi@tutu.tata      |
++------+---------------------+
 ```
 
 Example: create a hash and include values from preset named "config" of config file in this hash
@@ -1111,7 +1135,7 @@ It is also possible to provide a [Extended Value](#extended) in a file using `@j
 
 `ascli` configuration and other runtime files (token cache, file lists, persistency files, SDK) are stored `[config folder]`: `[User's home folder]/.aspera/ascli`.
 
-Note: `[User's home folder]` is found using ruby's `Dir.home` (`rb_w32_home_dir`).
+Note: `[User's home folder]` is found using Ruby's `Dir.home` (`rb_w32_home_dir`).
 It uses the `HOME` env var primarily, and on MS Windows it also looks at `%HOMEDRIVE%%HOMEPATH%` and `%USERPROFILE%`. `ascli` sets the env var `%HOME%` to the value of `%USERPROFILE%` if set and exists. So, on Windows `%USERPROFILE%` is used as it is more reliable than `%HOMEDRIVE%%HOMEPATH%`.
 
 The [config folder] can be displayed using :
@@ -1242,7 +1266,7 @@ ascli config preset get default _plugin_name_
 "_default_preset_for_plugin_"
 ```
 
-#### <a id="config"></a>Plugin: `config`: CLI Configuration
+#### <a id="config"></a>Plugin: `config`: Configuration
 
 Plugin `config` is used to configure `ascli` and also contains global options.
 
@@ -1265,9 +1289,11 @@ config ascp products list
 config ascp show
 config ascp spec
 config check_update
+config coffee
+config coffee --ui=text
+config detect --url=https://faspex4.example.com/path
 config detect --url=https://my_aoc_org.ibmaspera.com
-config detect --url=my_faspex_url
-config detect --url=my_node_url
+config detect --url=https://node_simple.example.com/path
 config doc
 config doc transfer-parameters
 config echo 'hello'
@@ -1280,7 +1306,7 @@ config echo @uri:/etc/hosts
 config echo @uri:file:/etc/hosts
 config echo @uri:http://www.ibm.com
 config echo @uri:https://www.ibm.com
-config echo @val:@file:yo
+config echo @val:@file:no_such_file
 config echo @zlib:@stdin:
 config email_test --notif-to=my_recipient_email
 config export
@@ -1313,15 +1339,15 @@ demo_server:
 
 We can see here:
 
-- The configuration was created with CLI version 0.3.7
+- The configuration was created with `ascli` version 0.3.7
 - the default [option preset](#lprt) to load for `server` plugin is : `demo_server`
 - the [option preset](#lprt) `demo_server` defines some parameters: the URL and credentials
 - the default [option preset](#lprt) to load in any case is : `cli_default`
 
 Two [option presets](#lprt) are reserved:
 
-- `config` contains a single value: `version` showing the CLI
-version used to create the configuration file. It is used to check compatibility.
+- `config` contains a single value: `version` showing the version used to create the configuration file.
+  It is used to check compatibility.
 - `default` is reserved to define the default [option preset](#lprt) name used for known plugins.
 
 The user may create as many [option presets](#lprt) as needed. For instance, a particular [option preset](#lprt) can be created for a particular application instance and contain URL and credentials.
@@ -1530,13 +1556,13 @@ Some applications allow the user to be authenticated using a private key (Server
 It consists in using a pair of keys: the private key and its associated public key.
 The same key can be used for multiple applications.
 Technically, a private key contains the public key, which can be extracted from it.
-The private key can be protected by a passphrase or not.
-If the key is protected by a passphrase, then it will be prompted.
+The file containing the private key can optionally be protected by a passphrase.
+If the key is protected by a passphrase, then it will be prompted when used.
 (some plugins support option `passphrase`)
 
 The following commands use the shell variable `PRIVKEYFILE`.
 Set it to the desired safe location of the private key.
-Typically, in `$HOME/.ssh` or `$HOME/.aspera/ascli`:
+Typically, located in folder `$HOME/.ssh` or `$HOME/.aspera/ascli`:
 
 ```bash
 PRIVKEYFILE=~/.aspera/ascli/my_private_key
@@ -1544,6 +1570,8 @@ PRIVKEYFILE=~/.aspera/ascli/my_private_key
 
 Several methods can be used to generate a key pair.
 
+The format expected for private keys is [PEM](https://en.wikipedia.org/wiki/Privacy-Enhanced_Mail).
+
 #### `ascli` for key generation
 
 The generated key is of type RSA, by default: 4096 bit.
@@ -1565,45 +1593,51 @@ ssh-keygen -t rsa -b 4096 -m PEM -N '' -f ${PRIVKEYFILE}
 #### `openssl`
 
 To generate a private key pair with a passphrase the following can be used on any system:
-<!-- spellchecker: disable -->
+
 ```bash
-openssl genrsa -passout pass:_passphrase_here_ -out ${PRIVKEYFILE}.protected 4096
+openssl genrsa -passout pass:_passphrase_here_ -out ${PRIVKEYFILE} 4096
 openssl rsa -pubout -in ${PRIVKEYFILE} -out ${PRIVKEYFILE}.pub
 ```
-<!-- spellchecker: enable -->
 
 `openssl` is sometimes compiled to support option `-nodes` (no DES, i.e. no passphrase, e.g. on macOS).
 In that case, add option `-nodes` instead of `-passout pass:_passphrase_here_` to generate a key without passphrase.
 
 If option `-nodes` is not available, the passphrase can be removed using this method:
 
-<!-- spellchecker: disable -->
 ```bash
-openssl rsa -passin pass:_passphrase_here_ -in ${PRIVKEYFILE}.protected -out ${PRIVKEYFILE}
-rm -f ${PRIVKEYFILE}.protected
+openssl rsa -passin pass:_passphrase_here_ -in ${PRIVKEYFILE} -out ${PRIVKEYFILE}.no_des
+mv ${PRIVKEYFILE}.no_des ${PRIVKEYFILE}
 ```
-<!-- spellchecker: enable -->
 
 To change (or add) the passphrase for a key do:
 
 ```bash
-openssl rsa -des3 -in old_file -out new_file
+openssl rsa -des3 -in ${PRIVKEYFILE} -out ${PRIVKEYFILE}.with_des
+mv ${PRIVKEYFILE}.with_des ${PRIVKEYFILE}
 ```
 
 ### <a id="certificates"></a>SSL CA certificate bundle
 
-`ascli` uses ruby `openssl` gem, which uses the `openssl` library.
-Certificates are checked against the ruby default certificates [OpenSSL::X509::DEFAULT_CERT_FILE](https://ruby-doc.org/stdlib-3.0.3/libdoc/openssl/rdoc/OpenSSL/X509/Store.html), which are typically the ones of `openssl` on Unix systems (Linux, macOS, etc..).
-The environment variables `SSL_CERT_FILE` and `SSL_CERT_DIR` are used if defined.
+`ascli` uses the Ruby `openssl` gem, which uses the `openssl` library.
+Certificates are checked against the [Ruby default certificate store](https://ruby-doc.org/stdlib-3.0.3/libdoc/openssl/rdoc/OpenSSL/X509/Store.html) `OpenSSL::X509::DEFAULT_CERT_FILE` and `OpenSSL::X509::DEFAULT_CERT_DIR`, which are typically the ones of `openssl` on Unix-like systems (Linux, macOS, etc..).
 
-`ascp` also needs to validate certificates when using WSS.
-By default, `ascp` uses primarily certificates from hard-coded path (e.g. on macOS: `/Library/Aspera/ssl`).
-`ascli` overrides and sets the default ruby certificate path as well for `ascp` using `-i` switch.
-So to update certificates, update ruby's `openssl` gem, or use env vars `SSL_CERT_*`.
+To display the current root certificate store locations:
+
+```bash
+ascli conf echo @ruby:'[OpenSSL::X509::DEFAULT_CERT_FILE,OpenSSL::X509::DEFAULT_CERT_DIR]'
+```
+
+Ruby's default values can be overridden by env vars: `SSL_CERT_FILE` and `SSL_CERT_DIR`.
+
+`ascp` also needs to validate certificates when using **WSS**.
+By default, `ascp` uses primarily certificates from hard-coded path (e.g. on macOS: `/Library/Aspera/ssl`) for WSS.
+`ascli` overrides and sets the default Ruby certificate path as well for `ascp` using `-i` switch.
+
+To update `ascli` trusted root certificates, just update your system's root certificates or use env vars specified here above.
 
 ### Plugins
 
-The CLI tool uses a plugin mechanism.
+`ascli` uses a plugin mechanism.
 The first level command (just after `ascli` on the command line) is the name of the concerned plugin which will execute the command.
 Each plugin usually represents commands sent to a specific application.
 For instance, the plugin `faspex` allows operations on the application "Aspera Faspex".
@@ -1697,7 +1731,7 @@ When `ascli` is used interactively in a shell, the shell itself will usually log
 
 ### Learning Aspera Product APIs (REST)
 
-This CLI uses REST APIs.
+`ascli` uses mainly Aspera applications REST APIs.
 To display HTTP calls, use argument `-r` or `--rest-debug`, this is useful to display exact content of HTTP requests and responses.
 
 In order to get traces of execution, use argument : `--log-level=debug`
@@ -1706,7 +1740,7 @@ In order to get traces of execution, use argument : `--log-level=debug`
 
 If the server does not provide a valid certificate, use option: `--insecure=yes`.
 
-Ruby HTTP socket parameters can be adjusted.
+HTTP socket parameters can be adjusted using option `http_options`:
 
 | parameter            | default |
 |----------------------|---------|
@@ -1716,8 +1750,8 @@ Ruby HTTP socket parameters can be adjusted.
 | `keep_alive_timeout` | 2       |
 
 Values are in set *seconds* and can be of type either integer or float.
-Default values are the ones of Ruby.
-For details refer to the Ruby library: [`Net::HTTP`](https://ruby-doc.org/stdlib/libdoc/net/http/rdoc/Net/HTTP.html).
+Default values are the ones of Ruby:
+refer to the Ruby library: [`Net::HTTP`](https://ruby-doc.org/stdlib/libdoc/net/http/rdoc/Net/HTTP.html).
 
 Like any other option, those can be set either on command line, or in config file, either in a global preset or server-specific one.
 
@@ -1734,7 +1768,7 @@ Some actions may require the use of a graphical tool:
 - a browser for Aspera on Cloud authentication (web auth method)
 - a text editor for configuration file edition
 
-By default the CLI will assume that a graphical environment is available on windows, and on other systems, rely on the presence of the "DISPLAY" environment variable.
+By default `ascli` assumes that a graphical environment is available on windows, and on other systems, rely on the presence of the `DISPLAY` environment variable.
 It is also possible to force the graphical mode with option --ui :
 
 - `--ui=graphical` forces a graphical environment, a browser will be opened for URLs or a text editor for file edition.
@@ -1870,7 +1904,7 @@ Saved to default global preset global_common_defaults
 
 Windows:
 
-```bash
+```text
 ascli config ascp use C:\Users\admin\.aspera\ascli\sdk\ascp.exe
 ```
 
@@ -1891,14 +1925,14 @@ ascli config ascp products list
 ```
 
 ```output
-:.........................................:................................................:
-:                  name                   :                    app_root                    :
-:.........................................:................................................:
-: Aspera Connect                          : /Users/laurent/Applications/Aspera Connect.app :
-: IBM Aspera CLI                          : /Users/laurent/Applications/Aspera CLI         :
-: IBM Aspera High-Speed Transfer Endpoint : /Library/Aspera                                :
-: Aspera Drive                            : /Applications/Aspera Drive.app                 :
-:.........................................:................................................:
++---------------------------------------+----------------------------------------+
+| name                                  | app_root                               |
++---------------------------------------+----------------------------------------+
+| IBM Aspera SDK                        | /Users/laurent/.aspera/ascli/sdk       |
+| Aspera Connect                        | /Applications/Aspera Connect.app       |
+| IBM Aspera CLI                        | /Users/laurent/Applications/Aspera CLI |
+| IBM Aspera High-Speed Transfer Server | /Library/Aspera                        |
++---------------------------------------+----------------------------------------+
 ```
 
 #### Selection of local client for `ascp` for [`direct`](#agt_direct) agent
@@ -1964,7 +1998,7 @@ Some of the actions on Aspera Applications lead to file transfers (upload and do
 When a transfer needs to be started, a [*transfer-spec*](#transferspec) has been internally prepared.
 This [*transfer-spec*](#transferspec) will be executed by a transfer client, here called **Transfer Agent**.
 
-There are currently 3 agents:
+There are currently 3 agents, set with option `transfer`:
 
 - [`direct`](#agt_direct) : a local execution of `ascp`
 - [`connect`](#agt_connect) : use of a local Connect Client
@@ -1978,6 +2012,8 @@ will effectively push files to the related server from the agent node.
 
 `ascli` standardizes on the use of a [*transfer-spec*](#transferspec) instead of *native* `ascp` options to provide parameters for a transfer session, as a common method for those three Transfer Agents.
 
+Specific options for agents are provided with option `transfer_info`, cumulatively.
+
 #### <a id="agt_direct"></a>Direct
 
 The `direct` agent directly executes a local `ascp`.
@@ -2052,22 +2088,82 @@ In addition to standard methods described in section [File List](#file_list), it
 >
 > **Note:** Those methods have limitations: they apply **only** to the [`direct`](#agt_direct) transfer agent (i.e. local `ascp`) and not for Aspera on Cloud.
 
+This agent supports a local configuration file: `aspera.conf` where Virtual links can be configured:
+
+On a server (HSTS), the following commands can be used to set a global virtual link:
+
+```bash
+asconfigurator -x 'set_trunk_data;id,1;trunk_name,in;trunk_capacity,45000;trunk_on,true'
+asconfigurator -x 'set_trunk_data;id,2;trunk_name,out;trunk_capacity,45000;trunk_on,true'
+asconfigurator -x 'set_node_data;transfer_in_bandwidth_aggregate_trunk_id,1'
+asconfigurator -x 'set_node_data;transfer_out_bandwidth_aggregate_trunk_id,2'
+```
+
+But this command is not available on clients, so edit the file `aspera.conf`, you can find the location with: `ascli conf ascp info --fields=aspera_conf` and modify the sections `default` and `trunks` like this for a global 100 Mbps virtual link:
+
+```xml
+<?xml version='1.0' encoding='UTF-8'?>
+<CONF version="2">
+    <default>
+        <transfer>
+            <in>
+                <bandwidth>
+                    <aggregate>
+                        <trunk_id>1</trunk_id>
+                    </aggregate>
+                </bandwidth>
+            </in>
+            <out>
+                <bandwidth>
+                    <aggregate>
+                        <trunk_id>2</trunk_id>
+                    </aggregate>
+                </bandwidth>
+            </out>
+        </transfer>
+    </default>
+    <trunks>
+        <trunk>
+            <id>1</id>
+            <name>in</name>
+            <on>true</on>
+            <capacity>
+                <schedule format="ranges">1000000</schedule>
+            </capacity>
+        </trunk>
+        <trunk>
+            <id>2</id>
+            <name>out</name>
+            <capacity>
+                <schedule format="ranges">1000000</schedule>
+            </capacity>
+            <on>true</on>
+        </trunk>
+    </trunks>
+</CONF>
+```
+
+It is also possible to set a schedule with different time and days, for example for the value of `schedule`:
+
+```text
+start=08 end=19 days=mon,tue,wed,thu capacity=900000;1000000
+```
+
 #### <a id="agt_connect"></a>IBM Aspera Connect Client GUI
 
 By specifying option: `--transfer=connect`, `ascli` will start transfers using the locally installed Aspera Connect Client. There are no option for `transfer_info`.
 
 #### <a id="agt_node"></a>Aspera Node API : Node to node transfers
 
-By specifying option: `--transfer=node`, the CLI will start transfers in an Aspera
-Transfer Server using the Node API, either on a local or remote node.
+By specifying option: `--transfer=node`, `ascli` starts transfers in an Aspera Transfer Server using the Node API, either on a local or remote node.
 Parameters provided in option `transfer_info` are:
 
-| Name | Type | Description |
-|------|------|-------------|
-| url | string | URL of the node API</br>Mandatory |
+| Name     | Type   | Description |
+|----------|--------|-------------|
+| url      | string | URL of the node API</br>Mandatory |
 | username | string | node api user or access key</br>Mandatory |
 | password | string | password, secret or bearer token</br>Mandatory |
-| root_id | string | password or secret</br>Mandatory only for bearer token |
+| root_id  | string | password or secret</br>Mandatory only for bearer token |
 
 Like any other option, `transfer_info` can get its value from a pre-configured [option preset](#lprt) :
 `--transfer-info=@preset:_name_here_` or be specified using the extended value syntax :
@@ -2120,8 +2216,8 @@ On Windows the compilation may fail for various reasons (3.1.1):
 
 ### <a id="transferspec"></a>Transfer Specification
 
-Some commands lead to file transfer (upload/download), all parameters necessary for this transfer
-is described in a [*transfer-spec*](#transferspec) (Transfer Specification), such as:
+Some commands lead to file transfer (upload/download).
+All parameters necessary for this transfer are described in a [*transfer-spec*](#transferspec) (Transfer Specification), such as:
 
 - server address
 - transfer user name
@@ -2129,9 +2225,13 @@ is described in a [*transfer-spec*](#transferspec) (Transfer Specification), suc
 - file list
 - etc...
 
-`ascli` builds a default [*transfer-spec*](#transferspec) internally, so it is not necessary to provide additional parameters on the command line for this transfer.
+`ascli` builds the [*transfer-spec*](#transferspec) internally, so it is not necessary to provide additional parameters on the command line for this transfer.
+
+The [*transfer-spec*](#transferspec) is a Hash (dictionary), so it is described on the command line with the [Extended Value Syntax](#extended).
 
-If needed, it is possible to modify or add any of the supported [*transfer-spec*](#transferspec) parameter using the `ts` option. The `ts` option accepts a [Structured Value](#native) containing one or several [*transfer-spec*](#transferspec) parameters. Multiple `ts` options on command line are cumulative.
+It is possible to modify or add any of the supported [*transfer-spec*](#transferspec) parameter using the `ts` option.
+The `ts` option accepts a [Structured Value](#native) containing one or several [*transfer-spec*](#transferspec) parameters in a `Hash`.
+Multiple `ts` options on command line are cumulative.
 
 It is possible to specify `ascp` options when the `transfer` option is set to [`direct`](#agt_direct) using `transfer_info` option parameter: `ascp_args`.
 Example: `--transfer-info=@json:'{"ascp_args":["-l","100m"]}'`.
@@ -2142,8 +2242,6 @@ The use of a [*transfer-spec*](#transferspec) instead of `ascp` parameters has t
 - common to all [Transfer Agent](#agents)
 - not dependent on command line limitations (special characters...)
 
-A [*transfer-spec*](#transferspec) is a Hash table, so it is described on the command line with the [Extended Value Syntax](#extended).
-
 ### <a id="transferparams"></a>Transfer Parameters
 
 All standard [*transfer-spec*](#transferspec) parameters can be specified.
@@ -2173,18 +2271,7 @@ Columns:
 Fields with EX_ prefix are extensions to transfer agent [`direct`](#agt_direct). (only in `ascli`).
 
 | Field | Type | D | N | C | Description |
-|-------|------|---|---|---|-------------|
-| EX_ascp_args | array | Y | &nbsp; | &nbsp; | Add native command line arguments to ascp |
-| EX_at_rest_password | string | Y | &nbsp; | &nbsp; | DEPRECATED: Prefer to use standard parameter: content_protection_password<br/>(env:ASPERA_SCP_FILEPASS) |
-| EX_file_list | string | Y | &nbsp; | &nbsp; | source file list |
-| EX_file_pair_list | string | Y | &nbsp; | &nbsp; | source file pair list |
-| EX_http_proxy_url | string | Y | &nbsp; | &nbsp; | Specify the proxy server address used by HTTP Fallback<br/>(-x {string}) |
-| EX_http_transfer_jpeg | int | Y | &nbsp; | &nbsp; | HTTP transfers as JPEG file<br/>(-j {int}) |
-| EX_license_text | string | Y | &nbsp; | &nbsp; | License file text override.<br/>By default ascp looks for license file near executable.<br/>(env:ASPERA_SCP_LICENSE) |
-| EX_no_read | bool | Y | &nbsp; | &nbsp; | no read source<br/>(--no-read) |
-| EX_no_write | bool | Y | &nbsp; | &nbsp; | no write on destination<br/>(--no-write) |
-| EX_proxy_password | string | Y | &nbsp; | &nbsp; | Password used for Aspera proxy server authentication.<br/>May be overridden by password in URL EX_fasp_proxy_url.<br/>(env:ASPERA_PROXY_PASS) |
-| EX_ssh_key_paths | array | Y | &nbsp; | &nbsp; | Use public key authentication for SSH and specify the private key file paths<br/>(-i {array}) |
+| ----- | ---- | - | - | - | ----------- |
 | apply_local_docroot | bool | Y | &nbsp; | &nbsp; | (--apply-local-docroot) |
 | authentication | string | &nbsp; | &nbsp; | Y | value=token for SSH bypass keys, else password asked if not provided. |
 | cipher | string | Y | Y | Y | In transit encryption type.<br/>Allowed values: none, aes-128, aes-192, aes-256, aes-128-cfb, aes-192-cfb, aes-256-cfb, aes-128-gcm, aes-192-gcm, aes-256-gcm<br/>(-c (conversion){enum}) |
@@ -2244,7 +2331,7 @@ Fields with EX_ prefix are extensions to transfer agent [`direct`](#agt_direct).
 | source_root_id | string | &nbsp; | Y | &nbsp; | The file ID of the source root directory. Required when using Bearer token auth for the source node. |
 | src_base | string | Y | Y | &nbsp; | Specify the prefix to be stripped off from each source object.<br/>The remaining portion of the source path is kept intact at the destination.<br/>Special care must be taken when used with cloud storage.<br/>(--src-base64 (conversion){string}) |
 | ssh_port | int | Y | Y | Y | Specifies SSH (TCP) port. Default: local:22, other:33001<br/>(-P {int}) |
-| ssh_private_key | string | Y | &nbsp; | &nbsp; | Private key used for SSH authentication.<br/>Shall look like: -----BEGIN RSA PRIV4TE KEY-----&sol;nMII...<br/>Note the JSON encoding: &sol;n for newlines.<br/>(env:ASPERA_SCP_KEY) |
+| ssh_private_key | string | Y | &nbsp; | &nbsp; | Private key used for SSH authentication.<br/>Shall look like: -----BEGIN RSA PRIV4TE KEY-----\nMII...<br/>Note the JSON encoding: \n for newlines.<br/>(env:ASPERA_SCP_KEY) |
 | ssh_private_key_passphrase | string | Y | &nbsp; | &nbsp; | The passphrase associated with the transfer user's SSH private key. Available as of 3.7.2.<br/>(env:ASPERA_SCP_PASS) |
 | sshfp | string | Y | Y | Y | Check it against server SSH host key fingerprint<br/>(--check-sshfp {string}) |
 | symlink_policy | string | Y | Y | Y | Handle source side symbolic links<br/>Allowed values: follow, copy, copy+force, skip<br/>(--symbolic-links {enum}) |
@@ -2257,6 +2344,17 @@ Fields with EX_ prefix are extensions to transfer agent [`direct`](#agt_direct).
 | use_ascp4 | bool | Y | Y | &nbsp; | specify version of protocol |
 | wss_enabled | bool | Y | Y | Y | Server has Web Socket service enabled |
 | wss_port | int | Y | Y | Y | TCP port used for websocket service feed |
+| EX_ascp_args | array | Y | &nbsp; | &nbsp; | DEPRECATED: Use parameter ascp_args in option transfer_info<br/>Add native command line arguments to ascp |
+| EX_at_rest_password | string | Y | &nbsp; | &nbsp; | DEPRECATED: Use standard spec parameter: content_protection_password<br/>Content protection password<br/>(env:ASPERA_SCP_FILEPASS) |
+| EX_file_list | string | Y | &nbsp; | &nbsp; | source file list |
+| EX_file_pair_list | string | Y | &nbsp; | &nbsp; | source file pair list |
+| EX_http_proxy_url | string | Y | &nbsp; | &nbsp; | Specify the proxy server address used by HTTP Fallback<br/>(-x {string}) |
+| EX_http_transfer_jpeg | int | Y | &nbsp; | &nbsp; | HTTP transfers as JPEG file<br/>(-j {int}) |
+| EX_license_text | string | Y | &nbsp; | &nbsp; | License file text override.<br/>By default ascp looks for license file near executable.<br/>(env:ASPERA_SCP_LICENSE) |
+| EX_no_read | bool | Y | &nbsp; | &nbsp; | no read source<br/>(--no-read) |
+| EX_no_write | bool | Y | &nbsp; | &nbsp; | no write on destination<br/>(--no-write) |
+| EX_proxy_password | string | Y | &nbsp; | &nbsp; | Password used for Aspera proxy server authentication.<br/>May be overridden by password in URL EX_fasp_proxy_url.<br/>(env:ASPERA_PROXY_PASS) |
+| EX_ssh_key_paths | array | Y | &nbsp; | &nbsp; | Use public key authentication for SSH and specify the private key file paths<br/>(-i {array}) |
 
 #### Destination folder for transfers
 
@@ -2331,7 +2429,7 @@ So, by default, the list of files to transfer will be simply specified on the co
     --sources=@lines:@stdin:
     ```
 
-  - Using ruby code (one path per line in file)
+  - Using Ruby code (one path per line in file)
 
     ```ruby
     --sources=@ruby:'File.read("myfilelist.txt").split("\n")'
@@ -2365,9 +2463,9 @@ ascli server upload --src-type=pair ~/Documents/Samples/200KB.1 /Upload/sample1
 
 #### <a id="multisession"></a>Support of multi-session
 
-Multi session, i.e. starting a transfer of a file set using multiple sessions (one `ascp` process per session) is supported on "direct" and "node" agents, not yet on connect.
+Multi session, i.e. starting a transfer of a file set using multiple sessions (one `ascp` process per session) is supported on `direct` and `node` agents, not yet on connect.
 
-- when agent=node :
+- `--transfer=node`
 
 ```bash
 --ts=@json:'{"multi_session":10,"multi_session_threshold":1}'
@@ -2375,7 +2473,7 @@ Multi session, i.e. starting a transfer of a file set using multiple sessions (o
 
 Multi-session is directly supported by the node daemon.
 
-- when agent=direct :
+- `--transfer=direct`
 
 ```bash
 --ts=@json:'{"multi_session":5,"multi_session_threshold":1,"resume_policy":"none"}'
@@ -2430,15 +2528,58 @@ Example: parameter to download a faspex package and decrypt on the fly
 --ts=@json:'{"precalculate_job_size":true}'
 ```
 
-### <a id="scheduling"></a>Scheduling
+### <a id="scheduler"></a>Scheduler
 
 It is useful to configure automated scheduled execution.
+`ascli` does not provide an internal scheduler.
+Instead, use the service provided by the Operating system:
+
+#### Windows Scheduler
+
+Windows provides the [Task Scheduler](https://docs.microsoft.com/en-us/windows/win32/taskschd/task-scheduler-start-page).
+It can be configured:
+
+- Using utility [`schtasks.exe`](https://learn.microsoft.com/fr-fr/windows-server/administration/windows-commands/schtasks-create)
+
+- Using powershell function [scheduletasks](https://learn.microsoft.com/en-us/powershell/module/scheduledtasks)
+
+- Using `taskschd.msc` (UI)
 
-#### <a id="locking"></a>Locking for exclusive execution
+#### Unix-like Scheduler
 
-It is also useful to ensure that `ascli` is not executed several times in parallel.
+Unix-like systems (Linux, ...) provide cron, configured using a [crontab](https://www.man7.org/linux/man-pages/man5/crontab.5.html)
 
-For instance when `ascli` is executed automatically on a schedule basis, one generally desire that a new execution is not started if a previous execution is still running because an on-going operation may last longer than the scheduling period:
+Linux also provides `anacron`, if tasks are hourly or daily.
+
+For example, on Linux it is convenient to create a wrapping script, e.g. `cron_ascli` that will setup the environment (e.g. Ruby) to properly start `ascli`:
+
+```bash
+#!/bin/bash
+# load the ruby environment
+. /etc/profile.d/rvm.sh
+rvm use 2.6 --quiet
+# set a timeout protection, just in case ascli is frozen 
+tmout=30m
+# forward arguments to ascli
+exec timeout ${tmout} ascli "${@}"
+```
+
+Example of cronjob created for user `xfer`.
+
+```bash
+crontab<<EOF
+0    * * * *  /home/xfer/cron_ascli preview scan --logger=syslog --display=error
+2-59 * * * *  /home/xfer/cron_ascli preview trev --logger=syslog --display=error
+EOF
+```
+
+> **Note:** The logging options are kept here in the cronfile instead of conf file to allow execution on command line with output on command line.
+
+### <a id="locking"></a>Locking for exclusive execution
+
+In some cases one needs to ensure that `ascli` is not executed several times in parallel.
+
+When `ascli` is executed automatically on a schedule basis, one generally desires that a new execution is not started if a previous execution is still running because an on-going operation may last longer than the scheduling period:
 
 - Executing instances may pile-up and kill the system
 - The same file may be transferred by multiple instances at the same time.
@@ -2456,7 +2597,7 @@ Usually the OS native scheduler already provides some sort of protection against
 `ascli` natively supports a locking mechanism with option `lock_port`.
 (Technically, this opens a local TCP server port, and fails if this port is already used, providing a local lock. Lock is released when process exits).
 
-Example:
+Testing `ascli` locking:
 
 Run this same command in two separate terminals within less than 30 seconds:
 
@@ -2470,18 +2611,6 @@ The first instance will sleep 30 seconds, the second one will immediately exit l
 WARN -- : Another instance is already running (Address already in use - bind(2) for "127.0.0.1" port 12345).
 ```
 
-#### <a id="scheduler"></a>Scheduler
-
-`ascli` does not provide an internal scheduler.
-
-Instead, use the service provided by the Operating system:
-
-- Windows: [Task Scheduler](https://docs.microsoft.com/en-us/windows/win32/taskschd/task-scheduler-start-page)
-- Linux/Unix: [cron](https://www.man7.org/linux/man-pages/man5/crontab.5.html)
-- etc...
-
-Linux also provides `anacron`, if tasks are hourly or daily.
-
 ### "Proven&ccedil;ale"
 
 `ascp`, the underlying executable implementing Aspera file transfer using FASP, has a capability to not only access the local file system (using system's `open`,`read`,`write`,`close` primitives), but also to do the same operations on other data storage such as S3, Hadoop and others. This mechanism is call *PVCL*. Several *PVCL* adapters are available, some are embedded in `ascp`
@@ -2608,7 +2737,7 @@ ascli server upload "faux:///mydir?file=testfile&count=1m&size=0&inc=2&seq=seque
 ```text
 ascli -h
 NAME
-        ascli -- a command line tool for Aspera Applications (v4.12.0)
+        ascli -- a command line tool for Aspera Applications (v4.13.0)
 
 SYNOPSIS
         ascli COMMANDS [OPTIONS] [ARGS]
@@ -2631,7 +2760,7 @@ COMMANDS
 OPTIONS
         Options begin with a '-' (minus), and value is provided on command line.
         Special values are supported beginning with special prefix @pfx:, where pfx is one of:
-        base64, json, zlib, ruby, csvt, lines, list, incps, vault, val, file, path, env, uri, stdin, preset
+        base64, csvt, env, file, json, lines, list, path, ruby, secret, stdin, uri, val, zlib, preset, incps, vault
         Dates format is 'DD-MM-YY HH:MM:SS', or 'now' or '-<num>h'
 
 ARGS
@@ -2700,7 +2829,7 @@ OPTIONS:
         --sources=VALUE              How list of transferred files is provided (@args,@ts,Array)
         --src-type=ENUM              Type of file list: list, pair
         --transfer=ENUM              Type of transfer agent: direct, node, connect, httpgw, trsdk
-        --transfer-info=VALUE        Parameters for transfer agent
+        --transfer-info=VALUE        Parameters for transfer agent (Hash)
         --progress=ENUM              Type of progress bar: none, native, multi
 
 
@@ -2714,7 +2843,7 @@ OPTIONS:
 
 
 COMMAND: node
-SUBCOMMANDS: access_key api_details asperabrowser async basic_token browse central delete download events health info license mkdir mkfile mklink rename search service space stream sync transfer upload watch_folder
+SUBCOMMANDS: access_key api_details asperabrowser async basic_token browse central delete download events health info license mkdir mkfile mklink rename search service space ssync stream sync transfer upload watch_folder
 OPTIONS:
         --url=VALUE                  URL of application, e.g. https://org.asperafiles.com
         --username=VALUE             username to log in
@@ -2723,7 +2852,7 @@ OPTIONS:
         --asperabrowserurl=VALUE     URL for simple aspera web ui
         --sync-name=VALUE            sync name
         --path=VALUE                 file or folder path for gen4 operation "file"
-        --token-type=ENUM            Type of token used for transfers: aspera, basic, hybrid
+        --token-type=ENUM            type of token used for transfers: aspera, basic, hybrid
         --default-ports=ENUM         use standard FASP ports or get from node api (gen4): [no], yes
 
 
@@ -2769,7 +2898,7 @@ OPTIONS:
 
 
 COMMAND: faspex5
-SUBCOMMANDS: admin bearer_token gateway health package postprocessing shared_folders user version
+SUBCOMMANDS: admin bearer_token gateway health packages postprocessing shared_folders user version
 OPTIONS:
         --url=VALUE                  URL of application, e.g. https://org.asperafiles.com
         --username=VALUE             username to log in
@@ -2777,10 +2906,12 @@ OPTIONS:
         --client-id=VALUE            OAuth client identifier
         --client-secret=VALUE        OAuth client secret
         --redirect-uri=VALUE         OAuth redirect URI for web authentication
-        --auth=ENUM                  OAuth type of authentication: boot, web, jwt
+        --auth=ENUM                  OAuth type of authentication: boot, link, web, jwt
+        --box=VALUE                  Package inbox, either shared inbox name or one of ["inbox", "inbox_history", "inbox_all", "inbox_all_history", "outbox", "outbox_history", "pending", "pending_history", "all"]
         --private-key=VALUE          OAuth JWT RSA private key PEM value (prefix file path with @file:)
         --passphrase=VALUE           RSA private key passphrase
         --shared-folder=VALUE        Shared folder source for package files
+        --link=VALUE                 public link for specific operation
 
 
 COMMAND: cos
@@ -2834,8 +2965,9 @@ OPTIONS:
         --thumb-text-font=VALUE      png: plaintext: font to render text with imagemagick convert (identify -list font)
         --video-conversion=ENUM      mp4: method for preview generation: [reencode], blend, clips
         --video-png-conv=ENUM        mp4: method for thumbnail generation: [fixed], animated
-        --video-start-sec=VALUE      mp4: start offset (seconds) of video preview
-        --video-scale=VALUE          mp4: video scale (ffmpeg)
+        --video-scale=VALUE          mp4: all: video scale (ffmpeg)
+        --video-start-sec=VALUE      mp4: all: start offset (seconds) of video preview
+        --reencode-ffmpeg=VALUE      mp4: reencode: options to ffmpeg
         --blend-keyframes=VALUE      mp4: blend: # key frames
         --blend-pauseframes=VALUE    mp4: blend: # pause frames
         --blend-transframes=VALUE    mp4: blend: # transition blend frames
@@ -2873,13 +3005,13 @@ OPTIONS:
         --validate-metadata=ENUM     Validate shared inbox metadata: [no], yes
 
 COMMAND: node
-SUBCOMMANDS: access_key api_details asperabrowser async basic_token browse central delete download events health info license mkdir mkfile mklink rename search service space stream sync transfer upload watch_folder
+SUBCOMMANDS: access_key api_details asperabrowser async basic_token browse central delete download events health info license mkdir mkfile mklink rename search service space ssync stream sync transfer upload watch_folder
 OPTIONS:
         --validator=VALUE            identifier of validator (optional for central)
         --asperabrowserurl=VALUE     URL for simple aspera web ui
         --sync-name=VALUE            sync name
         --path=VALUE                 file or folder path for gen4 operation "file"
-        --token-type=ENUM            Type of token used for transfers: aspera, basic, hybrid
+        --token-type=ENUM            type of token used for transfers: aspera, basic, hybrid
         --default-ports=ENUM         use standard FASP ports or get from node api (gen4): [no], yes
 
 
@@ -2962,7 +3094,7 @@ ascli config wizard --value=aoc
 
 Several types of OAuth authentication are supported:
 
-- JSON Web Token (JWT) : authentication is secured by a private key (recommended for CLI)
+- JSON Web Token (JWT) : authentication is secured by a private key (recommended for `ascli`)
 - Web based authentication : authentication is made by user using a browser
 - URL Token : external users authentication with url tokens (public links)
 
@@ -3004,7 +3136,6 @@ If you did not use the wizard, you can also manually create a [option preset](#l
 
 Lets create an [option preset](#lprt) called: `my_aoc_org` using `ask` interactive input (client info from previous step):
 
-<!-- spellchecker: disable -->
 ```bash
 ascli config preset ask my_aoc_org url client_id client_secret
 option: url> https://myorg.ibmaspera.com/
@@ -3012,7 +3143,6 @@ option: client_id> my_client_id_here
 option: client_secret> my_client_secret_here
 updated: my_aoc_org
 ```
-<!-- spellchecker: enable -->
 
 (This can also be done in one line using the command `config preset update my_aoc_org --url=...`)
 
@@ -3051,11 +3181,11 @@ ascli aoc admin res client list
 ```
 
 ```output
-:............:...............:
-:     id     :  name         :
-:............:...............:
-: my_BJbQiFw : my-client-app :
-:............:...............:
++------------+---------------+
+|     id     |  name         |
++------------+---------------+
+| my_BJbQiFw | my-client-app |
++------------+---------------+
 ```
 
 ```bash
@@ -3087,12 +3217,12 @@ ascli aoc admin res user list
 ```
 
 ```output
-:........:................:
-:   id   :      name      :
-:........:................:
-: 109952 : Tech Support   :
-: 109951 : LAURENT MARTIN :
-:........:................:
++--------+----------------+
+|   id   |      name      |
++--------+----------------+
+| 109952 | Tech Support   |
+| 109951 | LAURENT MARTIN |
++--------+----------------+
 ```
 
 ```ruby
@@ -3341,29 +3471,27 @@ ascli aoc admin res user create --bulk=yes @json:'[{"email":"dummyuser1@example.
 ```
 
 ```output
-:.......:.........:
-:  id   : status  :
-:.......:.........:
-: 98398 : created :
-: 98399 : created :
-:.......:.........:
++-------+---------+
+|  id   | status  |
++-------+---------+
+| 98398 | created |
+| 98399 | created |
++-------+---------+
 ```
 
 #### Example: Find with filter and delete
 
-<!-- spellchecker: disable -->
-
 ```bash
 ascli aoc admin res user list --query='@json:{"q":"dummyuser"}' --fields=id,email
 ```
 
 ```output
-:.......:........................:
-:  id   :         email          :
-:.......:........................:
-: 98398 : dummyuser1@example.com :
-: 98399 : dummyuser2@example.com :
-:.......:........................:
++-------+------------------------+
+|  id   |         email          |
++-------+------------------------+
+| 98398 | dummyuser1@example.com |
+| 98399 | dummyuser2@example.com |
++-------+------------------------+
 ```
 
 ```bash
@@ -3383,16 +3511,14 @@ ascli aoc admin res user --bulk=yes --id=@json:"$thelist" delete
 ```
 
 ```output
-:.......:.........:
-:  id   : status  :
-:.......:.........:
-: 98398 : deleted :
-: 98399 : deleted :
-:.......:.........:
++-------+---------+
+|  id   | status  |
++-------+---------+
+| 98398 | deleted |
+| 98399 | deleted |
++-------+---------+
 ```
 
-<!-- spellchecker: enable -->
-
 #### Example: <a id="deactuser"></a>Find deactivated users since more than 2 years
 
 ```ruby
@@ -3408,13 +3534,13 @@ ascli aoc user workspaces list
 ```
 
 ```output
-:......:............................:
-:  id  :            name            :
-:......:............................:
-: 16   : Engineering                :
-: 17   : Marketing                  :
-: 18   : Sales                      :
-:......:............................:
++------+----------------------------+
+|  id  |            name            |
++------+----------------------------+
+| 16   | Engineering                |
+| 17   | Marketing                  |
+| 18   | Sales                      |
++------+----------------------------+
 ```
 
 #### Example: Create a sub access key in a "node"
@@ -3454,16 +3580,16 @@ ascli aoc admin res workspace_membership list --fields=member_type,manager,membe
 ```
 
 ```output
-:.............:.........:..................................:
-: member_type : manager :           member.email           :
-:.............:.........:..................................:
-: user        : true    : john.curtis@email.com            :
-: user        : false   : laurent.martin.aspera@fr.ibm.com :
-: user        : false   : jean.dupont@me.com               :
-: user        : false   : another.user@example.com         :
-: group       : false   :                                  :
-: user        : false   : aspera.user@gmail.com            :
-:.............:.........:..................................:
++-------------+---------+----------------------------------+
+| member_type | manager |           member.email           |
++-------------+---------+----------------------------------+
+| user        | true    | john.curtis@email.com            |
+| user        | false   | laurent.martin.aspera@fr.ibm.com |
+| user        | false   | jean.dupont@me.com               |
+| user        | false   | another.user@example.com         |
+| group       | false   |                                  |
+| user        | false   | aspera.user@gmail.com            |
++-------------+---------+----------------------------------+
 ```
 
 Other query parameters:
@@ -3519,12 +3645,12 @@ ascli aoc admin res user list --fields=email --query=@json:'{"q":"last_login_at:
 ```
 
 ```output
-:...............................:
-:             email             :
-:...............................:
-: John.curtis@acme.com          :
-: Jean.Dupont@tropfort.com      :
-:...............................:
++-------------------------------+
+|             email             |
++-------------------------------+
+| John.curtis@acme.com          |
+| Jean.Dupont@tropfort.com      |
++-------------------------------+
 ```
 
 #### Example: List "Limited" users
@@ -3615,8 +3741,6 @@ ascli -Paoc_show aoc files transfer --from-folder='IBM Cloud SJ' --to-folder='AW
 
 #### Example: create registration key to register a node
 
-<!-- spellchecker: disable -->
-
 ```bash
 ascli aoc admin res client create @json:'{"data":{"name":"laurentnode","client_subject_scopes":["alee","aejd"],"client_subject_enabled":true}}' --fields=token --format=csv
 ```
@@ -3642,8 +3766,6 @@ ascli aoc admin res client list --fields=id --format=csv|ascli aoc admin res cli
 +-----+---------+
 ```
 
-<!-- spellchecker: enable -->
-
 #### Example: Create a Node
 
 AoC nodes as actually composed with two related entities:
@@ -3755,7 +3877,7 @@ When user packages are listed, the following query is used:
 {"archived":false,"exclude_dropbox_packages":true,"has_content":true,"received":true}
 ```
 
-To list packages in a shared inbox, the query has to be specified with withe the shared inbox by name or its identifier.
+To list packages in a shared inbox, the query has to be specified with the the shared inbox by name or its identifier.
 Additional parameters can be specified, as supported by the API (to find out available filters, consult the API definition, or use the web interface in developer mode).
 The current workspace is added unless specified in the query.
 
@@ -4022,8 +4144,10 @@ aoc files rename /somefolder testdst
 aoc files short_link create --to-folder=/testdst --value=private
 aoc files short_link create --to-folder=/testdst --value=public
 aoc files short_link list --value=@json:'{"purpose":"shared_folder_auth_link"}'
-aoc files sync admin status --to-folder=/testdst --sync-info=@json:'{"sessions":[{"name":"s2","direction":"pull","local_dir":"syncdir","reset":true}]}'
-aoc files sync start --to-folder=/testdst --sync-info=@json:'{"sessions":[{"name":"s2","direction":"pull","local_dir":"syncdir","reset":true}]}'
+aoc files sync ad st --sync-info=@json:'{"name":"syncv2","reset":true,"direction":"pull","local":{"path":"my_local_sync_dir"},"remote":{"path":"/testdst"}}'
+aoc files sync ad st --sync-info=@json:'{"sessions":[{"name":"syncv1","direction":"pull","local_dir":"my_local_sync_dir","remote_dir":"/testdst","reset":true}]}'
+aoc files sync start --sync-info=@json:'{"name":"syncv2","reset":true,"direction":"pull","local":{"path":"my_local_sync_dir"},"remote":{"path":"/testdst"}}'
+aoc files sync start --sync-info=@json:'{"sessions":[{"name":"syncv1","direction":"pull","local_dir":"my_local_sync_dir","remote_dir":"/testdst","reset":true}]}'
 aoc files transfer --from-folder=/testsrc --to-folder=/testdst testfile.bin
 aoc files upload --to-folder=/ testfile.bin --link=my_aoc_publink_folder
 aoc files upload --to-folder=/testsrc testfile.bin
@@ -4069,8 +4193,6 @@ If you are using ATS as part of AoC, then authentication is through AoC, not IBM
 
 First get your IBM Cloud APIkey. For instance, it can be created using the IBM Cloud web interface, or using command line:
 
-<!-- spellchecker: disable -->
-
 ```bash
 ibmcloud iam api-key-create mykeyname -d 'my sample key'
 ```
@@ -4090,6 +4212,7 @@ UUID          ApiKey-05b8fadf-e7fe-4bc4-93a9-6fd348c5ab1f
 ```
 
 References:
+<!-- spellchecker: disable -->
 
 - [https://console.bluemix.net/docs/iam/userid_keys.html#userapikey](https://console.bluemix.net/docs/iam/userid_keys.html#userapikey)
 - [https://ibm.ibmaspera.com/helpcenter/transfer-service](https://ibm.ibmaspera.com/helpcenter/transfer-service)
@@ -4098,8 +4221,6 @@ References:
 
 Then, to register the key by default for the ats plugin, create a preset. Execute:
 
-<!-- spellchecker: disable -->
-
 ```bash
 ascli config preset update my_ibm_ats --ibm-api-key=my_secret_api_key_here
 ```
@@ -4138,8 +4259,6 @@ ascli ats api_key create
 ascli config preset update my_ibm_ats --ats-key=ats_XXXXXXXXXXXXXXXXXXXXXXXX --ats-secret=YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
 ```
 
-<!-- spellchecker: enable -->
-
 ### <a id="ats_params"></a>ATS Access key creation parameters
 
 When creating an ATS access key, the option `params` must contain an extended value with the creation parameters.
@@ -4214,7 +4333,6 @@ then commands `ascp` (for transfers) and `ascmd` (for file operations) are execu
 ### Server sample commands
 
 ```bash
-server br /
 server browse /
 server browse NEW_SERVER_FOLDER/testfile.bin
 server browse folder_1/target_hot
@@ -4232,10 +4350,10 @@ server md5sum NEW_SERVER_FOLDER/testfile.bin
 server mkdir NEW_SERVER_FOLDER --logger=stdout
 server mkdir folder_1/target_hot
 server mv folder_1/200KB.2 folder_1/to.delete
-server sync admin status --sync-info=@json:'{"name":"sync2","local":{"path":"syncdir"}}'
-server sync admin status --sync-session=mysync --sync-info=@json:'{"sessions":[{"name":"mysync","local_dir":"syncdir"}]}'
-server sync start --sync-info=@json:'{"name":"sync2","local":{"path":"syncdir"},"remote":{"path":"'"NEW_SERVER_FOLDER"'"},"reset":true,"quiet":false}'
-server sync start --sync-info=@json:'{"sessions":[{"name":"mysync","direction":"pull","remote_dir":"'"NEW_SERVER_FOLDER"'","local_dir":"syncdir","reset":true}]}'
+server sync admin status --sync-info=@json:'{"name":"sync2","local":{"path":"my_local_sync_dir"}}'
+server sync admin status --sync-session=mysync --sync-info=@json:'{"sessions":[{"name":"mysync","local_dir":"my_local_sync_dir"}]}'
+server sync start --sync-info=@json:'{"name":"sync2","local":{"path":"my_local_sync_dir"},"remote":{"path":"'"NEW_SERVER_FOLDER"'"},"reset":true,"quiet":false}'
+server sync start --sync-info=@json:'{"sessions":[{"name":"mysync","direction":"pull","remote_dir":"'"NEW_SERVER_FOLDER"'","local_dir":"my_local_sync_dir","reset":true}]}'
 server upload --sources=@ts --ts=@json:'{"EX_ascp_args":["--file-list","'"filelist.txt"'"]}' --to-folder=NEW_SERVER_FOLDER 
 server upload --sources=@ts --ts=@json:'{"EX_ascp_args":["--file-pair-list","'"filepairlist.txt"'"]}'
 server upload --sources=@ts --ts=@json:'{"EX_file_list":"'"filelist.txt"'"}' --to-folder=NEW_SERVER_FOLDER
@@ -4277,9 +4395,9 @@ ascli server --ssh-keys=@list:,~/.ssh/id_rsa
 ascli server --ssh-keys=@json:'["~/.ssh/id_rsa"]'
 ```
 
-For file operation command (browse, delete), the ruby SSH client library `Net::SSH` is used and provides several options settable using option `ssh_options`.
+For file operation command (browse, delete), the Ruby SSH client library `Net::SSH` is used and provides several options settable using option `ssh_options`.
 
-For a list of SSH client options, refer to the ruby documentation of [Net::SSH](http://net-ssh.github.io/net-ssh/Net/SSH.html#method-c-start).
+For a list of SSH client options, refer to the Ruby documentation of [Net::SSH](http://net-ssh.github.io/net-ssh/Net/SSH.html#method-c-start).
 
 Some of the 50 available SSH options:
 
@@ -4301,7 +4419,7 @@ or on Windows:
 ERROR -- net.ssh.authentication.agent: could not connect to ssh-agent: pageant process not running
 ```
 
-This means that your environment suggessts to use an agent but you don't have such an SSH agent running, then:
+This means that your environment suggests to use an agent but you don't have such an SSH agent running, then:
 
 - Check env var: `SSH_AGENT_SOCK`
 - Check your file: `$HOME/.ssh/config`
@@ -4341,6 +4459,8 @@ ascli server download /aspera-test-dir-large/200MB
 
 This plugin gives access to capabilities provided by HSTS node API.
 
+> **Note:** capabilities of this plugin are used in other plugins which access to the node API, such as `aoc`.
+
 ### File Operations
 
 It is possible to:
@@ -4369,7 +4489,8 @@ For transfers, it is possible to control how transfer is authorized using option
 
 ### Central
 
-The central subcommand uses the "reliable query" API (session and file). It allows listing transfer sessions and transferred files.
+The central subcommand uses the "reliable query" API (session and file).
+It allows listing transfer sessions and transferred files.
 
 Filtering can be applied:
 
@@ -4398,16 +4519,12 @@ Refer to [Aspera documentation](https://download.asperasoft.com/download/docs/en
 - Start watchd and watchfolderd services running as a system user having access to files
 - configure a watchfolder to define automated transfers
 
-<!-- spellchecker: disable -->
-
 ```bash
 ascli node service create @json:'{"id":"mywatchd","type":"WATCHD","run_as":{"user":"user1"}}'
 ascli node service create @json:'{"id":"mywatchfolderd","type":"WATCHFOLDERD","run_as":{"user":"user1"}}'
 ascli node watch_folder create @json:'{"id":"mywfolder","source_dir":"/watch1","target_dir":"/","transport":{"host":"10.25.0.4","user":"user1","pass":"mypassword"}}'
 ```
 
-<!-- spellchecker: enable -->
-
 ### Out of Transfer File Validation
 
 Follow the Aspera Transfer Server configuration to activate this feature.
@@ -4417,11 +4534,11 @@ ascli node central file list --validator=ascli --data=@json:'{"file_transfer_fil
 ```
 
 ```output
-:..............:..............:............:......................................:
-: session_uuid :    file_id   :   status   :              path                    :
-:..............:..............:............:......................................:
-: 1a74444c-... : 084fb181-... : validating : /home/xfer.../PKG - my title/200KB.1 :
-:..............:..............:............:......................................:
++--------------+--------------+------------+--------------------------------------+
+| session_uuid |    file_id   |   status   |              path                    |
++--------------+--------------+------------+--------------------------------------+
+| 1a74444c-... | 084fb181-... | validating | /home/xfer.../PKG - my title/200KB.1 |
++--------------+--------------+------------+--------------------------------------+
 ```
 
 ```bash
@@ -4447,6 +4564,28 @@ ascli node download /share/sourcefile --to-folder=/destination_folder --preset=a
 
 This will get transfer information from the SHOD instance and tell the Azure ATS instance to download files.
 
+### node file information
+
+When node api is used with an **Access key**, extra information can be retrieved, such as preview.
+
+> **Note:** Display of preview on terminal requires installation of extra gem: `rmagick`
+
+```bash
+gem install rmagick
+```
+
+For example it is possible to display the preview of a file, if it exists, using:
+
+```bash
+ascli aoc files file thumbnail --path=/preview_samples/Aspera.mpg
+```
+
+Using direct node access and an access key , one can do:
+
+```bash
+ascli node access_key do self file thumbnail --path=/preview_samples/Aspera.mpg
+```
+
 ### Create access key
 
 ```bash
@@ -4456,14 +4595,15 @@ ascli node access_key create --value=@json:'{"id":"myaccesskey","secret":"my_sec
 ### Node sample commands
 
 ```bash
-node access_key create --value=@json:'{"id":"aoc_1","storage":{"type":"local","path":"/"}}'
-node access_key delete aoc_1
+node access_key create --value=@json:'{"id":"testingAK1","storage":{"type":"local","path":"/"}}'
+node access_key delete testingAK1
 node access_key do my_aoc_ak_name browse /
 node access_key do my_aoc_ak_name delete /folder2
 node access_key do my_aoc_ak_name delete testfile1
 node access_key do my_aoc_ak_name download testfile1 --to-folder=.
 node access_key do my_aoc_ak_name file show --path=/testfile1
 node access_key do my_aoc_ak_name file show 1
+node access_key do my_aoc_ak_name file thumbnail --path=/testfile1
 node access_key do my_aoc_ak_name find /
 node access_key do my_aoc_ak_name mkdir /folder1
 node access_key do my_aoc_ak_name node_info /
@@ -4481,7 +4621,7 @@ node basic_token
 node browse / -r
 node delete /todelete
 node delete @list:,folder_1/todelete,folder_1/tdlink,folder_1/delfile
-node delete folder_1/10MB.1
+node delete folder_1/10MB.2
 node delete testfile.bin
 node download testfile.bin --to-folder=.
 node download testfile.bin --to-folder=. --token-type=hybrid
@@ -4497,19 +4637,23 @@ node service create @json:'{"id":"service1","type":"WATCHD","run_as":{"user":"us
 node service delete service1
 node service list
 node space /
-node sync bandwidth my_syncid
-node sync counters my_syncid
-node sync create --value=@json:'{"configuration":{"name":"sync1","local":{"path":"my_local_path"},"remote":{"host":"my_host","port":my_port,"user":"my_username","pass":"my_password","path":"my_remote_path"}}}'
-node sync delete my_syncid
-node sync files my_syncid
-node sync list
-node sync show my_syncid
-node sync start my_syncid
-node sync state my_syncid
-node sync stop my_syncid
-node sync summary my_syncid
+node ssync bandwidth my_syncid
+node ssync counters my_syncid
+node ssync create --value=@json:'{"configuration":{"name":"sync1","local":{"path":"my_local_path"},"remote":{"host":"my_host","port":my_port,"user":"my_username","pass":"my_password","path":"my_remote_path"}}}'
+node ssync delete my_syncid
+node ssync files my_syncid
+node ssync list
+node ssync show my_syncid
+node ssync start my_syncid
+node ssync state my_syncid
+node ssync stop my_syncid
+node ssync summary my_syncid
+node sync ad st --sync-info=@json:'{"name":"syncv2","reset":true,"direction":"pull","local":{"path":"my_local_sync_dir"},"remote":{"path":"/aspera-test-dir-tiny"}}'
+node sync ad st --sync-info=@json:'{"sessions":[{"name":"syncv1","direction":"pull","local_dir":"my_local_sync_dir","remote_dir":"/aspera-test-dir-tiny","reset":true}]}'
+node sync start --sync-info=@json:'{"name":"syncv2","reset":true,"direction":"pull","local":{"path":"my_local_sync_dir"},"remote":{"path":"/aspera-test-dir-tiny"}}'
+node sync start --sync-info=@json:'{"sessions":[{"name":"syncv1","direction":"pull","local_dir":"my_local_sync_dir","remote_dir":"/aspera-test-dir-tiny","reset":true}]}'
 node transfer list --value=@json:'{"active_only":true}'
-node upload --to-folder="folder_1" --sources=@ts --ts=@json:'{"paths":[{"source":"/aspera-test-dir-small/10MB.1"}],"precalculate_job_size":true}' --transfer=node --transfer-info=@json:'{"url":"my_node_url","username":"my_node_user","password":"my_node_pass_here"}'
+node upload --to-folder=folder_1 --sources=@ts --ts=@json:'{"paths":[{"source":"/aspera-test-dir-small/10MB.2"}],"precalculate_job_size":true}' --transfer=node --transfer-info=@json:'{"url":"my_node_url","username":"my_node_user","password":"my_node_pass_here"}'
 node upload --username=my_aoc_ak_name --password=my_aoc_ak_secret testfile.bin --token-type=basic
 node upload testfile.bin --to-folder=folder_1 --ts=@json:'{"target_rate_cap_kbps":10000}'
 node upload testfile.bin --to-folder=folder_1 --ts=@json:'{"target_rate_cap_kbps":10000}' --token-type=hybrid
@@ -4593,6 +4737,9 @@ Then `ascli` will lookup existing contacts, and if a single match is found will
 
 > **Note:** The lookup is case insensitive and on partial matches.
 
+On reception, option `box` (default to `inbox`) can be set to the same values as API accepts, or to the name of a shared inbox.
+If the value `ALL` is provided to option `box`, then all packages are selected.
+
 ### Faspex 5 sample commands
 
 Most commands are directly REST API calls.
@@ -4606,20 +4753,24 @@ faspex5 admin res accounts list
 faspex5 admin res contacts list
 faspex5 admin res jobs list
 faspex5 admin res metadata_profiles list
-faspex5 admin res node list --value=@json:'{"type":"received","subtype":"mypackages"}'
+faspex5 admin res node list 
 faspex5 admin res oauth_clients list
 faspex5 admin res registrations list
 faspex5 admin res saml_configs list
 faspex5 admin res shared_inboxes list
 faspex5 admin res workgroups list
+faspex5 admin smtp show
+faspex5 admin smtp test my_email_external
 faspex5 bearer_token
 faspex5 gateway --value=https://localhost:12345/aspera/faspex &\
 faspex5 health
-faspex5 package list --value=@json:'{"mailbox":"inbox","state":["released"]}'
-faspex5 package receive "my_package_id" --to-folder=.  --ts=@json:'{"content_protection_password":"abc123_yo"}'
-faspex5 package send --value=@json:'{"title":"test title","recipients":["my_shinbox"],"metadata":{"Options":"Opt1","TextInput":"example text"}}' testfile.bin
-faspex5 package send --value=@json:'{"title":"test title","recipients":[{"name":"my_f5_user"}]}' testfile.bin --ts=@json:'{"content_protection_password":"my_passphrase_here"}'
-faspex5 package show "my_package_id"
+faspex5 packages list --value=@json:'{"mailbox":"inbox","state":["released"]}'
+faspex5 packages receive "my_package_id" --to-folder=.  --ts=@json:'{"content_protection_password":"abc123_yo"}'
+faspex5 packages receive ALL --once-only=yes --to-folder=.
+faspex5 packages receive INIT --once-only=yes
+faspex5 packages send --value=@json:'{"title":"test title","recipients":["my_shinbox"],"metadata":{"Options":"Opt1","TextInput":"example text"}}' testfile.bin
+faspex5 packages send --value=@json:'{"title":"test title","recipients":[{"name":"my_f5_user"}]}' testfile.bin --ts=@json:'{"content_protection_password":"my_passphrase_here"}'
+faspex5 packages show "my_package_id"
 faspex5 postprocessing --value=@json:'{"url":"https://localhost:8443/domain","processing":{"script_folder":"tests"},"certificate":{"key":"../local/k","cert":"../local/c","chain":"../local/ch"}}' &\
 faspex5 user profile modify @json:'{"preference":{"connect_disabled":false}}'
 faspex5 user profile show
@@ -4627,6 +4778,16 @@ faspex5 user profile show
 
 Other examples:
 
+- list packages
+
+  The following parameters in option `value` are supported:
+
+  - `q` : a filter on name (case insensitive, matches if value is contained in name)
+  - `max` : maximum number of items to retrieve (stop pages when the maximum is passed)
+  - `pmax` : maximum number of pages to request (stop pages when the maximum is passed)
+  - `offset` : native api parameter, in general do not use (added by `ascli`)
+  - `limit` : native api parameter, number of items par api call, in general do not use (added by `ascli`)
+
 - Send a package with metadata
 
 The interface is the one of the API (Refer to API documentation, or look at request in browser):
@@ -4669,6 +4830,20 @@ ascli faspex5 shared_folders br 3 /folder
 ascli faspex5 package send --value=@json:'{"title":"hello","recipients":[{"name":"_recipient_here_"}]}' --shared-folder=3 /folder/file
 ```
 
+- receive all packages (cargo)
+
+To receive all packages, only once, through persistency of already received packages:
+
+```bash
+ascli faspex5 packages receive ALL --once-only=yes
+```
+
+To initialize, and skip all current package so that next time `ALL` is used, only newer packages are downloaded:
+
+```bash
+ascli faspex5 packages receive INIT --once-only=yes
+```
+
 ### Faspex 4-style postprocessing script with Faspex 5
 
 `ascli` provides command `postprocessing` in plugin `faspex5` to emulate Faspex 4 postprocessing.
@@ -4684,12 +4859,12 @@ The following parameters are supported:
 
 | parameter                  | type    | default                | description                                         |
 |----------------------------|---------|------------------------|-----------------------------------------------------|
-| url                        | string  | http://localhost:8080  | Defines the base url on which requests are listened |
+| url                        | string  | <http://localhost:8080>  | Defines the base url on which requests are listened |
 | certificate                | hash    | nil                    | used to define certificate if https is used         |
 | certificate.key            | string  | nil                    | path to private key file                            |
 | certificate.cert           | string  | nil                    | path to certificate                                 |
 | certificate.chain          | string  | nil                    | path to intermediary certificates                   |
-| processing                 | hash    | nil                    | behaviour of post processing                        |
+| processing                 | hash    | nil                    | behavior of post processing                        |
 | processing.script_folder   | string  | .                      | prefix added to script path                         |
 | processing.fail_on_error   | bool    | false                  | if true and process exit with non zero, then fail   |
 | processing.timeout_seconds | integer | 60                     | processing script is killed if takes more time      |
@@ -4704,7 +4879,7 @@ When a request is received the following happens:
 
 - the processor get the path of the url called
 - it removes the "domain
-- it pre-prends it with the value of `script_folder`
+- it prepends it with the value of `script_folder`
 - it executes the script
 - upon success, a success code is returned
 
@@ -4752,7 +4927,8 @@ As inboxes may be large, it is possible to use the following query parameters:
 
 The API is listed in [Faspex 4 API Reference](https://developer.ibm.com/apis/catalog/?search=faspex) under "Services (API v.3)".
 
-If no parameter `max` or `pmax` is provided, then all packages will be listed in the inbox, which result in paged API calls (using parameter: `count` and `page`). By default page is `0` (`10`), it can be increased to have less calls.
+If no parameter `max` or `pmax` is provided, then all packages will be listed in the inbox, which result in paged API calls (using parameter: `count` and `page`).
+By default `count` is `0` (`10`), it can be increased to issue less HTTP calls.
 
 #### Example: list packages in dropbox
 
@@ -4879,18 +5055,18 @@ faspex package list --recipient="*my_faspex_dbx" --format=csv --fields=package_i
 faspex package list --recipient="*my_faspex_wkg" --format=csv --fields=package_id --query=@json:'{"max":1}'
 faspex package recv "my_package_id" --to-folder=.
 faspex package recv "my_package_id" --to-folder=. --box=sent
-faspex package recv --to-folder=. --link="my_faspex_publink_recv_from_fxuser"
+faspex package recv --to-folder=. --link=https://app.example.com/recv_from_user_path
 faspex package recv ALL --to-folder=. --once-only=yes
 faspex package recv my_pkgid --recipient="*my_faspex_dbx" --to-folder=.
 faspex package recv my_pkgid --recipient="*my_faspex_wkg" --to-folder=.
 faspex package send --delivery-info=@json:'{"title":"Important files delivery","recipients":["*my_faspex_dbx"]}' testfile.bin
 faspex package send --delivery-info=@json:'{"title":"Important files delivery","recipients":["*my_faspex_wkg"]}' testfile.bin
 faspex package send --delivery-info=@json:'{"title":"Important files delivery","recipients":["my_email_internal_user","my_faspex_username"]}' testfile.bin
-faspex package send --link="my_faspex_publink_send_to_dropbox" --delivery-info=@json:'{"title":"Important files delivery"}' testfile.bin
-faspex package send --link="my_faspex_publink_send_to_fxuser" --delivery-info=@json:'{"title":"Important files delivery"}' testfile.bin
+faspex package send --link=https://app.example.com/send_to_dropbox_path --delivery-info=@json:'{"title":"Important files delivery"}' testfile.bin
+faspex package send --link=https://app.example.com/send_to_user_path --delivery-info=@json:'{"title":"Important files delivery"}' testfile.bin
 faspex source list
-faspex source name "my_source_name" info
-faspex source name "my_source_name" node br /
+faspex source name my_faspex_src info
+faspex source name my_faspex_src node br /
 faspex v4 dmembership list
 faspex v4 dropbox list
 faspex v4 metadata_profile list
@@ -4901,7 +5077,7 @@ faspex v4 workgroup list
 
 ## <a id="shares"></a>Plugin: `shares`: IBM Aspera Shares v1
 
-Aspera Shares supports the "node API" for the file transfer part. (Shares 1 and 2)
+Aspera Shares supports the "node API" for the file transfer part.
 
 ### Shares 1 sample commands
 
@@ -5011,8 +5187,6 @@ ibmcloud resource service-key _service_key_name_here_ --output JSON|jq '.[0].cre
 
 It consists in the following structure:
 
-<!-- spellchecker: disable -->
-
 ```json
 {
   "apikey": "my_api_key_here",
@@ -5029,8 +5203,6 @@ It consists in the following structure:
 }
 ```
 
-<!-- spellchecker: enable -->
-
 The field `resource_instance_id` is for option `crn`
 
 The field `apikey` is for option `apikey`
@@ -5076,20 +5248,30 @@ cos node upload testfile.bin
 
 ## <a id="async"></a>Plugin: `async`: IBM Aspera Sync
 
-A basic plugin to start an "async" using `ascli`.
-The main advantage over bare `async` command line is the possibility to use a configuration file, using `ascli` standard options.
+A basic plugin to start an `async` using `ascli`.
+The main advantage over bare `async` command line is the possibility to use a configuration file, using standard options of `ascli`.
 
-Also, the `sync` command is also made available through the `server sync` and `aoc files sync` commands.
-In this case, some of the `sync` parameters are fill from parameters of the related plugin.
+The `sync` command is also made available through the `server sync`, `aoc files sync` and `node sync` commands.
+In this case, some of the `sync` parameters are filled by the related plugin using transfer spec parameters (including token).
 
 > **Note:** All `sync` commands require an `async` enabled license and availability of the `async` executable (and `asyncadmin`).
->
-> **Note:** Two JSON syntax are supported for option `sync_info`.
-> The first is same sync payload as specified on the `async` option `--conf` or in the latest node API, this is the preferred syntax and allows a single session definition.
-> The second (legacy) is specific to `ascli` and allows definition of multiple sync sessions in a single command, although usually only one sync session is defined.
+
+Two JSON syntax are supported for option `sync_info`.
+
+### async native JSON
+
+It is the same payload as specified on the `async` option `--conf` or in the latest node API.
+This is the preferred syntax and allows a single session definition.
+But there is no progress output nor error messages.
 
 Documentation on Async node API can be found on [IBM Developer Portal](https://developer.ibm.com/apis/catalog?search=%22aspera%20sync%20api%22).
 
+### async options as JSON
+
+This is specific to `ascli`.
+It is based on a JSON representation of `async` command line options.
+It allows definition of multiple sync sessions in a single command, although usually only one sync session is defined.
+
 ### Sync sample commands
 
 ```bash
@@ -5194,7 +5376,6 @@ dnf install unoconv
 
 - Amazon Linux
 
-<!-- spellchecker: disable -->
 ```bash
 amazon-linux-extras enable libreoffice
 yum clean metadata
@@ -5203,15 +5384,17 @@ wget https://raw.githubusercontent.com/unoconv/unoconv/master/unoconv
 mv unoconv /usr/bin
 chmod a+x /usr/bin/unoconv
 ```
-<!-- spellchecker: enable -->
 
 ### Configuration
 
-The preview generator is run as a user, preferably a regular user (not root). When using object storage, any user can be used, but when using local storage it is usually better to use the user `xfer`, as uploaded files are under this identity: this ensures proper access rights. (we will assume this)
+The preview generator should be executed as a non-user.
+When using object storage, any user can be used, but when using local storage it is usually better to use the user `xfer`, as uploaded files are under this identity: this ensures proper access rights. (we will assume this)
 
-Like any `ascli` commands, parameters can be passed on command line or using a configuration [option preset](#lprt).  The configuration file must be created with the same user used to run so that it is properly used on runtime.
+Like any `ascli` commands, parameters can be passed on command line or using a configuration [option preset](#lprt).
+The configuration file must be created with the same user used to run so that it is properly used on runtime.
 
-The `xfer` user has a special protected shell: `aspshell`, so changing identity requires specification of alternate shell:
+The `xfer` user has a special protected shell: `aspshell`, so in order to update the configuration, and when changing identity, specify an alternate shell.
+E.g.:
 
 ```bash
 su -s /bin/bash - xfer
@@ -5232,11 +5415,17 @@ ascli -Ppreviewconf node browse /
 
 This shall list the contents of the storage root of the access key.
 
+### Options for generated files
+
+When generating preview files, some options are provided by default.
+Some values for the options can be modified on command line.
+For video preview, the whole set of options can be overridden with option `reencode_ffmpeg`: it is a Hash with two keys: `in` and `out`, each is an array of strings with the native options to `ffmpeg`.
+
 ### Execution
 
 The tool intentionally supports only a **one shot** mode (no infinite loop) in order to avoid having a hanging process or using too many resources (calling REST api too quickly during the scan or event method).
 It needs to be run on a regular basis to create or update preview files.
-For that use your best reliable scheduler, see [Scheduling](#scheduling).
+For that use your best reliable scheduler, see [Scheduler](#scheduler).
 
 Typically, for **Access key** access, the system/transfer is `xfer`. So, in order to be consistent have generate the appropriate access rights, the generation process should be run as user `xfer`.
 
@@ -5254,36 +5443,15 @@ On subsequent run it reads this file and check that previews are generated for t
 
 ### Configuration for Execution in scheduler
 
-Here is an example of configuration for use with `cron` on Linux.
-Adapt the scripts to your own needs.
-
-We assume here that a configuration preset was created as shown previously.
+Details are provided in section [Scheduler](#scheduler).
 
-Lets first setup a script that will be used in the scheduler and set up the environment.
+Shorter commands can be specified if a configuration preset was created as shown previously.
 
-Example of startup script `cron_ascli`, which sets the Ruby environment and adds some timeout protection:
+For example the timeout value can be differentiated depending on the option: event versus scan:
 
-<!-- spellchecker: disable -->
 ```bash
- #!/bin/bash
- # set a timeout protection, just in case
 case "$*" in *trev*) tmout=10m ;; *) tmout=30m ;; esac
-. /etc/profile.d/rvm.sh
-rvm use 2.6 --quiet
-exec timeout ${tmout} ascli "${@}"
 ```
-<!-- spellchecker: enable -->
-
-Here the cronjob is created for user `xfer`.
-
-```bash
-crontab<<EOF
-0    * * * *  /home/xfer/cron_ascli preview scan --logger=syslog --display=error
-2-59 * * * *  /home/xfer/cron_ascli preview trev --logger=syslog --display=error
-EOF
-```
-
-> **Note:** The logging options are kept here in the cronfile instead of conf file to allow execution on command line with output on command line.
 
 ### Candidate detection for creation or update (or deletion)
 
@@ -5325,8 +5493,8 @@ For instance to filter out files beginning with `._` do:
 
 Two types of preview can be generated:
 
-- png: thumbnail
-- mp4: video preview (only for video)
+- `png`: thumbnail
+- `mp4`: video preview (only for video)
 
 Use option `skip_format` to skip generation of a format.
 
@@ -5391,7 +5559,7 @@ yum install shared-mime-info
 brew install shared-mime-info
 ```
 
-### Access to original files and preview creation
+### Generation: Read source files and write preview
 
 Standard open source tools are used to create thumbnails and video previews.
 Those tools require that original files are accessible in the local file system and also write generated files on the local file system.
@@ -5406,7 +5574,7 @@ If the preview generator does not have access to files on the file system (it is
 
 ```bash
 preview check --skip-types=office
-preview folder 1 --skip-types=office --log-level=info --file-access=remote --ts=@json:'{"target_rate_kbps":1000000}'
+preview scan --scan-id=1 --skip-types=office --log-level=info --file-access=remote --ts=@json:'{"target_rate_kbps":1000000}'
 preview scan --skip-types=office --log-level=info
 preview test --case=test mp4 my_file_mxf --video-conversion=blend --log-level=debug
 preview test --case=test mp4 my_file_mxf --video-conversion=clips --log-level=debug
@@ -5421,10 +5589,11 @@ preview trevents --once-only=yes --skip-types=office --log-level=info
 
 ## SMTP for email notifications
 
-Aspera CLI can send email, for that setup SMTP configuration. This is done with option `smtp`.
+`ascli` can send email, for that setup SMTP configuration. This is done with option `smtp`.
 
 The `smtp` option is a hash table (extended value) with the following fields:
 
+<!-- markdownlint-disable MD034 -->
 | field        | default             | example                    | description                      |
 |--------------|---------------------|----------------------------|----------------------------------|
 | `server`     | -                   | smtp.gmail.com             | SMTP server address              |
@@ -5435,6 +5604,7 @@ The `smtp` option is a hash table (extended value) with the following fields:
 | `password`   | -                   | my_password_here           | password for above username      |
 | `from_email` | username if defined | johnny@example.com         | address used if receiver replies |
 | `from_name`  | same as email       | John Wayne                 | display name of sender           |
+<!-- markdownlint-enable MD034 -->
 
 ### Example of configuration
 
@@ -5548,7 +5718,7 @@ There are special "extended" [*transfer-spec*](#transferspec) parameters support
 | required additional components to `ascp` | Ruby<br/>Aspera | - | library<br/>(headers) | daemon |
 | startup | JSON on stdin<br/>(standard APIs:<br/>JSON.generate<br/>Process.spawn) | command line arguments | API | daemon |
 | events | JSON on stdout | none by default<br/>or need to open management port<br/>and proprietary text syntax | callback | callback |
-| platforms | any with ruby and `ascp` | any with `ascp` (and SDK if compiled) | any with `ascp` | any with `ascp` and transfer daemon |
+| platforms | any with Ruby and `ascp` | any with `ascp` (and SDK if compiled) | any with `ascp` | any with `ascp` and transfer daemon |
 
 ### Simple session
 
@@ -5646,7 +5816,7 @@ Interesting `ascp` features are found in its arguments: (see `ascp` manual):
 >
 > **Note:** Most, but not all, native `ascp` arguments are available as standard [*transfer-spec*](#transferspec) parameters.
 >
-> **Note:** Only for the [`direct`](#agt_direct) transfer agent (not others, like connect or node), native `ascp` arguments can be provided option `transfer_info` parameter `ascp_args`.
+> **Note:** Only for the [`direct`](#agt_direct) transfer agent (not others, like connect or node), native `ascp` arguments can be provided with parameter `ascp_args` of option `transfer_info` .
 
 #### server side and configuration
 
@@ -5659,7 +5829,7 @@ Virtually any transfer on a "repository" on a regular basis might emulate a hot
 #### Scheduling
 
 Once `ascli` parameters are defined, run the command using the OS native scheduler, e.g. every minutes, or 5 minutes, etc...
-Refer to section [Scheduling](#scheduling). (on use of option `lock_port`)
+Refer to section [Scheduler](#scheduler). (on use of option `lock_port`)
 
 ### Example: upload hot folder
 
@@ -5739,30 +5909,7 @@ Main components:
 - `Aspera::Fasp`: starting and monitoring transfers. It can be considered as a FASPManager class for Ruby.
 - `Aspera::Cli`: `ascli`.
 
-A working example can be found in the gem, example:
-
-```bash
-ascli config gem path
-```
-
-```bash
-cat $(ascli config gem path)/../examples/transfer.rb
-```
-
-This sample code shows some example of use of the API as well as REST API.
-Note: although nice, it's probably a good idea to use RestClient for REST.
-
-Example of use of the API of Aspera on Cloud:
-
-```ruby
-require 'aspera/aoc'
-
-aoc=Aspera::AoC.new(url: 'https://sedemo.ibmaspera.com',auth: :jwt, scope: 'user:all', private_key: File.read(File.expand_path('~/.aspera/ascli/aspera_on_cloud_key')),username: 'laurent.martin.aspera@fr.ibm.com',subpath: 'api/v1')
-
-aoc.read('self')
-```
-
-<https://github.com/IBM/aspera-cli/blob/main/examples/aoc.rb>
+Working examples can be found in repo: <https://github.com/laurent-martin/aspera-api-examples> in Ruby examples.
 
 ## Changes (Release notes)
 
@@ -5790,6 +5937,13 @@ So, it evolved into `ascli`:
 Over the time, a supported command line tool `aspera` was developed in C++, it was later on deprecated.
 It had the advantage of being relatively easy to installed, as a single executable (well, still using `ascp`), but it was too limited IMHO, and lacked a lot of the features of this CLI.
 
+Enjoy a coffee on me:
+
+```bash
+ascli conf coffee
+ascli conf coffee --ui=text
+```
+
 ## Common problems
 
 ### Error: "Remote host is not who we expected"
@@ -5810,7 +5964,7 @@ References: ES-1944 in release notes of 4.1 and to [HSTS admin manual section "C
 
 Some Ruby gems dependencies require compilation of native parts (C).
 This also requires Ruby header files.
-If Ruby was installed as a Linux Packages, then also install ruby development package:
+If Ruby was installed as a Linux Packages, then also install Ruby development package:
 `ruby-dev` ir `ruby-devel`, depending on distribution.
 
 ### ED255519 key not supported
@@ -5823,5 +5977,5 @@ Without this deactivation, if such key was present the following error was gener
 OpenSSH keys only supported if ED25519 is available
 ```
 
-Which meant that you do not have ruby support for ED25519 SSH keys.
+Which meant that you do not have Ruby support for ED25519 SSH keys.
 You may either install the suggested Gems, or remove your ed25519 key from your `.ssh` folder to solve the issue.