|
#1
|
|||
|
|||
Problems with FTP
Using Process Files and the FTP step, I am trying to copy my build to our FTP server. However, this method doesn't work. First off, having the FTP connection opened and closed for every file is very inefficient and our server thinks you are doing bad things when you reconnect very rapidly in a short period of time.
Secondly, using this method won't build a directory tree (or at least I can't find a option that will do this) so I end up with all of my files copied to one flat folder instead of it containing the appropriate sub directories. Is there anything I can do to get around this? |
#2
|
|||
|
|||
The Process Files method does result in a new connection for each file. Adding a Wait step in the loop to pause between each file may help, depending on the delay required by your server. The next release of VBP will have recursive put built into the FTP action (using a single connection for all files).
See the Recurse.bld sample (Update Web Site section) for how to recursively put files into subfolders to match the source. |
#3
|
|||
|
|||
I used the %PROCFILES_FILE_DIR% as shown in the Recurse.bld sample and that did the trick for building the directory tree properly.
I added a 10 second wait between files which made the FTP server happy, but it makes the transfer really slow. How long before the next update to VBP? Thanks |
#4
|
|||
|
|||
Using wildcards (e.g. *) in the FTP step will speed up things considerably.
I suggest using the "Process once for each folder" option in the Process Files Option together with the wildcard option in FTP which would do one connect for each subdirectory instead of one connect for each file |
#5
|
|||
|
|||
That's an excellent suggestion (I neglected to mention that the Recurse.bld sample also demonstrates that).
We're currently targetting Nov. for the next release. |
|
|