Ever since using Wappler, we have setup almost all our/client’s projects to upload to various shared hosting servers. Every time we save a file, with the target selected as FTP, it “connects” to the server, then uploads it. This time of connecting and uploading ranges from 3 seconds to 20 seconds - with frequent failure every 10-15th upload.
I have tried setting USE ACTIVE option in target thinking it will not try to “connect” every single time I save a file, but it does not work that way. It basically does not do anything for me.
I do see a slightly better speeds when uploading multiple files, but its rare.
Next is the publish option, which is the main disaster for me. I have basically stopped doing a publish since past 4 months or so.
From the output window, I see that it first reads each and every folder-subfolder and file on the remote server, then it starts uploading files one by one, again taking same amount of time “reading” as it did earlier, and then additional time in uploading the file actually.
Now, if I just copy the same folder/files via FileZilla (similar to what publish or save does), it takes almost fraction of the time Wappler takes. FileZilla also does a check on each file/folder/sub-folder etc but it does not cause any issues. So there is no internet issue on my or server’s end for sure.
- Saving file on Wappler with FTP target, connects to FTP first always, and then uploads the file. There is no active connection kind of functionality.
- Doing full publish takes forever.
- Both normal upload and publish-like upload from FileZilla always takes fraction of the time Wappler takes.
So, is there something I have been doing wrong since the beginning or is it a Wappler shortcoming which has not been reported before, hence not been improved upon?
Or, is this some issue with shared hosting, FTP & Wappler (reminder: shared hosting, FTP & FileZilla works fine)?