2,032
edits
PHP Uploads: Difference between revisions
m
→MaxConcurrentUploads
| (5 intermediate revisions by 2 users not shown) | |||
|
It can transfer both text and binary files.
If the ''upload.php'' file is installed for CMX and the protocol works for CMX then it will also work for CUtils and the file locations will be relative to the location of the ''upload.php'' file (which therefore will be the root location of your website).
'''Note''': It is not a requirement to change to using the PHP Upload method. The previous FTP/FTPS/SFTP methods remain fully supported and operational.
== Is it secure? ==
:* If any updates fail, then only the cumulative data since the last successful transfer is sent.
:* It uses data compression over the network
== Disadvantages? ==
* It requires PHP support from your web provider - though most do
* Some web providers may not permit all the PHP methods that are required to implement this method
* You need to change your upload paths to use the new method - make a copy of your Cumulus.ini and your cumulusutils.ini file so you can easily revert
== Configuration ==
This option should only be used if you are certain, you need it, and ideally you can restrict the PHP process file system permissions to the areas you want data written.
=== CumulusUtils ===
The CUtils inifile parameter ''UploadDir'' specifies a subdirectory for CUtils relative to the webroot (the location of ''upload.php'') without any specification of the URL (as that is implicit in the use of ''upload.PHP'' as specified in ''Cumulus.ini''). If you wish all files to be transferred into the same directory as specified by CMX, then leave ''UploadDir'' empty.
If you run ''CumulusUtils'' for ''[[Website Generator|website]]'' without [[Thrifty - Cutils Command Qualifier|Thrifty]] it may generate a lot of files which need to be uploaded. So many that your server may refuse uploads at a certain point. To avoid the uploads to fail CUtils has two optimisations for the PHP upload protocol:
==== MaxConcurrentUploads ====
Just like you can in CMX, you may define the number of concurrent downloads which your server can handle. The parameter ''MaxConcurrentUploads'' defaults to no value which means it takes the value you defined in CMX. IIf you give this parameter a value, that value overrides the CMX value.
==== delayMilliSeconds ====
Some servers have a limit to the number of HTTP Post requests can be handled (e.g. 10 per second). If that is the case you need to define a delay value for the time between uploads. This is defined with the
''delayMilliSeconds'' parameter which defaults to 0 meaning the uploads secced each other as fast as possible.
== Cumulus.ini ==
| |||