FTP upload and web page display errors

[Karen K]

If you try to open a web page while the FTP uploader is uploading it, you get an incomplete display. It is a very short time only, but if you look at the Google Search Console you see, even Google recognizes this problem sometimes. The thread Page not found or empty suggests to use rsync instead of FTP to avoid those problems. Unfortunately, rsync is not available with all web space providers or you have to book a much bigger plan for that which is much more expensive.

From time to time I thought about these things during the last months. The web space providers may not offer rsync, but they always offer a database. Databases prevent incomplete data by transaction control. So, what about using the database for that purpose?

So I tried this idea, and I would like to present the result here. I tried it with the WeeWX built-in Seasons skin, and it is working.

I had looked for a solution that does not require changes to the skin itself, and I found a way to do so. 

Of course there is a better way by adjusting the skin itself, but I guess, that is not the way most of the users would want to go.

[Karen K]

I put a short description of the issue in german on our website on the WeeWX page.

[Karen K]

There is an enhancement to SQLupload. If you cannot use MQTT for whatever reason to show live data, uploading the LOOP packets by SQL may be an alternative approach. This is supported now. (Of course, it requires adjustments to the skin. And it needs more tests to make sure there are no hidden bugs.)

[Karen K]

I am not sure, if I measured that right, but it seems to me that uploading by SQL is much faster than uploading by pure FTP. If I remember that right, it took the FTP uploader about 30 seconds to upload all the files. Now it takes about 7.5 seconds for SQL upload and about 6.5 seconds for the FTP upload of the remaining files.