Date: Tue, 19 Mar 2024 07:49:40 +0000 (UTC) Message-ID: <467154291.19511.1710834580828@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_19510_1786192606.1710834580828" ------=_Part_19510_1786192606.1710834580828 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Please check the P= arameter Reference Documentation for an overview of the available YADE = parameters.
WebDAV support is subject to the following issues:
First we create some global profiles for file transfer from a WebDAV hos= t to a localhost:
[local_= target_host] target_protocol =3D local target_dir =3D /tmp/test/jade/in [webdav_source_host] source_protocol =3D webdav source_host =3D http://homer.sos/jade source_port =3D 80 source_user =3D test source_password =3D 12345 source_ssh_auth_method =3D url [copy_webdav2local] include =3D webdav_source_host,local_target_host operation =3D copy
The profile copy_webdav2local will be included in further profi= les.
In the file_path option you can add a list of source file names= .
If the option source_dir is empty then these file names hav= e to be specified with absolute paths from the viewpoint of the WebDAV serv= er (e.g. DocumentRoot setting in Apache).
In this example there are two files with the same name in different sour= ce directories: /jade/out/1.txt and /jade/out2/1.txt
After the transfer there is only one file /tmp/test/jade/in/1.txt in the target directory.
This is a special situation and a good example to discuss the difference=
in behaviour depending on the options overwrite_files (default: <=
code>true) and append_files (default: false
).<=
/p>
Here we have three profiles:
[filepa= th_append] include =3D copy_webdav2local file_path =3D /jade/out/1.txt;/jade/out2/1.txt append_files =3D true=20 [filepath_no_overwrite] include =3D copy_webdav2local file_path =3D /jade/out/1.txt;/jade/out2/1.txt overwrite_files =3D false [filepath_overwrite] include =3D copy_webdav2local file_path =3D /jade/out/1.txt;/jade/out2/1.txt
You can also use
file_pa= th =3D 1.txt;../out2/1.txt source_dir =3D /jade/out/
or
file_pa= th =3D out/1.txt;out2/1.txt source_dir =3D /jade/
instead of the above setting
file_pa= th =3D /jade/out/1.txt;/jade/out2/1.txt
The file_spec option expects a regular expression to select fil= es from the directory that is specified by the source_dir option.<= /p>
false
) is used to transfer all files with names=
ending in .txt from subdirectories of source_dir[filesp= ec] include =3D copy_webdav2local source_dir =3D /jade/out file_spec =3D \.txt$ [recursive] include =3D copy_webdav2local source_dir =3D /jade/out file_spec =3D \.txt$ recursive =3D true
First we create a global profile for the proxy parameter:
[webdav_= source_proxy] source_proxy_host =3D proxy.sos source_proxy_port =3D 3128 #source_proxy_user =3D=20 #source_proxy_password =3D
The profile webdav_source_proxy will be included in above f= ile_spec profile:
[filespe= c_with_proxy] include =3D copy_webdav2local,webdav_source_proxy source_dir =3D /jade/out file_spec =3D \.txt$
and so you receive the above example with file_spec with= proxy support.
First we create some global profiles for file transfer from the localhos= t to a WebDAV server:
[local_= source_host] source_protocol =3D local [webdav_target_host] target_protocol =3D webdav target_host =3D http://homer.sos/jade target_port =3D 80 target_user =3D test target_password =3D 12345 target_ssh_auth_method =3D url target_dir =3D /jade/in [copy_local2webdav] include =3D webdav_target_host,local_source_host operation =3D copy
The profile copy_local2webdav will be included in further profi= les.
Please note that the target_dir has to be specified as absolute= path from the viewpoint of the WebDAV server (e.g. DocumentRoot s= etting in Apache).
The target_dir is not relative to the location in which WebDAV = is operated.
This example is similar to the above example with file_path for transfer f= rom WebDAV host to localhost, however, the direction has changed.
[filepa= th] include =3D copy_local2webdav file_path =3D /tmp/test/jade/in/1.txt
The append_files parameter is reported not to have worked for s= ome releases. Using this parameter prevents /tmp/test/jade/out2/1.= txt from overwriting /tmp/test/jade/out/1.txt as by= the following profile:
[filepa= th_append] include =3D copy_local2webdav file_path =3D /tmp/test/jade/out/1.txt;/tmp/test/jade/out2/1.t= xt append_files =3D true=20
These examples are similar to the above example with file_sp= ec, however, directions have changed.
false
) is used to transfer files with names ending i=
n .txt from subdirectories of source_dir[filespe= c] include =3D copy_local2webdav source_dir =3D /tmp/test/jade/out file_spec =3D \.txt$ [recursive] include =3D copy_local2webdav source_dir =3D /tmp/test/jade/out file_spec =3D \.txt$ recursive =3D true
First we create a global profile for the proxy parameter:
[webdav_= target_proxy] target_proxy_host =3D proxy.sos target_proxy_port =3D 3128 #target_proxy_user =3D=20 #target_proxy_password =3D
The profile webdav_target_proxy will be included in above f= ile_spec profile:
[filespe= c_with_proxy] include =3D copy_local2webdav,webdav_target_proxy source_dir =3D /tmp/test/jade/out file_spec =3D \.txt$
as a result you receive the above example with file_spec with proxy support.