Replies: 1 comment
-
Direct Git support will be available in the future as is - we had plans to abandon Github Pages and Gitlab Pages support, but in the last months we have decided that we will still support these methods. Regarding Regarding I think that for your requirements you can consider custom build - I did not use this platform, but I see that they have such option: https://fleek.xyz/docs/platform/deployments/ Then you can remove unnecessary files or replace content of |
Beta Was this translation helpful? Give feedback.
-
Publii is replacing important files when deploying (Syncing) an update to Git Repository.
_redirects
(this is an IPFS formatted redirect file)..gitignore
file. (otherwise,.DS_Store
files keep getting deployed again to the repo automatically).We have have tested other methods a little, and we are aware that Publii plans to remove direct Git support, but we think it should be kept if possible so our updates are deployed easier, and we don't ever plan to use centralized hosting such as Github Pages, or any kind of centralized hosting in the future.
Currently, we have to perform a fetch, manually replacing the files that Publii deletes when the Sync is executed, and push a second commit for each update. Having a specific branch for Publii is also another option, but, is about the same amount of work each update anyways.
Beta Was this translation helpful? Give feedback.
All reactions