2.1 deploy

deploy web site

2.1.1 Description

collect all htm files and put then onto web site

check, which files have to be deleted, which to be updated. Then copy htm files to web site.

2.1.2 Options

--notUsed -e (value)

bla bla bla

--deployTargetHost (value)

IP address or domain name where web site should be deployed to Host to which the complete web site is deployed.

--deployTargetWeb (value)

directory on the deployTargetHost, where html pages should be put to. this directory should already exist. It is reachable from where the FTP command puts one when logging in.

--help -h (flag )

Print a short help message, listing the options. Just a short listing of all available options. In case of records (AKA record commands) before the options a list of its fields is printed. For deeper and more information use man or better info.

--verbose -v (flag )

Let this command talk to you a lot. When this option is set, the command produces a lot of output. This output is written to stderr. This makes it possible to use the verbose mode even, if the actual data is transported via stdout. Without this options the comannd is more or less quiet, except when errors ocurre.

--version (flag )

Display version information. The version information available for command is printed. This is the release number, the RCS identifier and the date of last save the source. This three values are given for the command specification and for the command implementation.

--output -o (value)

File to which output is written. Says to which file the output should be written. In future it will be extended by a complex data direction system.

--error (value)

Format specification of the stderr output like logging. This is the output description for the output send via the siliconBrainLib XML printer. Standard value is –logging, which makes output without any tag names and without attribute names. Other good values are –tty or –xml. –bash is also a trial worth.

--complete (flag )

Indicate completeness of specified options. No further lookup in configuration chain. The configuration chain is a number of locations, in which the options processing is looking for specifications of command and package options (all package options are command options as well). These locations are looked up in a predefined sequence. This is the configuration chain. An option is taken from the first location where it is found. The first location to look is the command line options followed by the environment variables then a configuration placed in the current directory, home directory, /etc. For performance reasons or other, the –complete option stops further lookup in the configuation chain. For example using –complete in the command line will avoid reading the environment. The configurationReader will always set this option, because it has read the complete chain already.