When you do that, you can select your PHP version, and you can assign your domain name to the Web Application. That is like a virtual host in the web server. Next you need to create a Web Application. It will probably take about 15 to 20 minutes for the process to complete, and once you are done, you can start to manage your server from within the web panel. You will get a very long one-line command like this.Īll that you need to do is run the command in your server as the root user and let it run. When your server is ready, you go back to RunCloud and enter your server details like the IP address to get your connection command. Throughout this tutorial I used a Linode VPS which costs $5 per month. With RunCloud, what you need to do is deploy a fresh Ubuntu 16.04 LTS VPS on almost any VPS hosting provider. If you don’t fancy using your social media account, then just use your email address.
You don’t need a credit card and you can even use your Facebook, Google, or GitHub account. When I look at the transfer in the config window of Mirall, it appears that the upload itself is very fast ( open called for ownclouds:///owncloudbeta/remote.php/webdav/Liban/Liban (38).JPGġ1-28 15:22:33:331 oc_module: Stating directory ownclouds:///owncloudbeta/remote.php/webdav/Libanġ1-28 15:22:33:331 oc_module: Dir ownclouds:///owncloudbeta/remote.php/webdav/Liban is there, we know it already.ġ1-28 15:22:33:331 oc_module: PUT request on /owncloudbeta/remote.php/webdav/Liban/Liban%20%2838%29.JPG!ġ1-28 15:22:33:331 oc_module: Sendfile handling request type PUT. It takes 3.5 seconds to upload a picture of 1,39 Mo. Just for information, I just tested Mirall 1.5 1.4.2 against OC 6 RC (realeased today). (This is probably tricky because as far as I understand, the way csync handles transfers is limited to handling only a single file at a time.) do a single PROPFIND for a collection and evaluate all its members for changes from that one multistatus response (later, the PROPFIND depth could be increased even further, in theory up to requesting the complete remote hierarchy en bloc).Īlso, wouldn't it be possible to extend the owncloud implementation of the PUT command to support passing the modification time as a request header when uploading the file so that no additional PROPPATCH request is necessary after the upload?Īs suggested above, when actually transferring file data, batching several transfers in parallel could increase throughput. Maybe as a first step it would help to batch the metadata operations concerning the same collection, i.e. This also already affects walking the the remote filesystem when checking for modifications. I think the problem is primarily due to the overhead per file/collection (reading/setting props, caching the file locally etc.) which ends up being more costly than the actual data transfer for small files and collections.
IMHO this also has to do with having a deep directory hierarchy. I can confirm this issue (OC 4.5.5, Linux client 1.1.4).
0 kommentar(er)
