Open GasmoN opened 5 years ago
Sounds great. But of course, when tags are used - probably often to create Categories - then you'll have more than 30 new items to upload.
Sounds great. But of course, when tags are used - probably often to create Categories - then you'll have more than 30 new items to upload.
Are you saying that tags would be the problem or..? I don' fully understand what you are trying to say.
@GasmoN - which deployment method are you using?
You have wrote:
Instead of using currently Sync method where you regenerate and reupload the whole project, I think that there should be additional button to generate and upload only new or changed files.
Publii uploads only files which has been modified, so the amount of uploaded files after creating new posts strictly depends on fact how your theme is built. E.g. if your theme displays new posts in many places (for example - under every post) then you will get many files to upload as many files is changed.
But in most cases after creating new post, there is only few files to upload.
@GasmoN - which deployment method are you using?
You have wrote:
Instead of using currently Sync method where you regenerate and reupload the whole project, I think that there should be additional button to generate and upload only new or changed files.
Publii uploads only files which has been modified, so the amount of uploaded files after creating new posts strictly depends on fact how your theme is built. E.g. if your theme displays new posts in many places (for example - under every post) then you will get many files to upload as many files is changed.
But in most cases after creating new post, there is only few files to upload.
I use FTP Deployment, and I just noticed that publii anways reupload default folders files (amp, assets, etc.)
@GasmoN - please check if the files.publii.json exists on your server and if it has a correct permissions. We have uploaded many times Publii websites using FTP to many servers and we didn't noticed this kind of issues.
@dziudek I think that .json file didn't on my server when I used to sync new files, but I can't test now since I don't have webserver anymore. I hope someone will test this eventually.
I have found that Publii resets the file date on every file in my site when syncing to a manual output folder, but since most of the files are genuinely unchanged, it gives me a way out: I use the manual output followed by rclone to synch the local folder to my website. (I have to do this anyway because I am on FastMail and the only protocol supported is WebDav.) So rclone can be persuaded to upload only changed files by means of the --checksum option, which switches time-stamp comparison for checksum comparison. My site went from syncing 2900+ files to ~30. Sync time drops from almost an hour to 3 minutes.
I think that this feature is requered for those of us who want to use publii for daily news website. What's is all about? Instead of using currently Sync method where you regenerate and reupload the whole project, I think that there should be additional button to generate and upload only new or changed files. That way, if you add about 30 news daily, you won't need to wait that long for the whole project to be regenerated and reuploaded to your web server.
EDIT: Another suggestion is to manually select files (posts, tags, etc) we want to render and upload. That way, after every post we write, we could select it and upload. And because it's only one post it will take only a few seconds.