3 ms·
When you press save once, the changes are applied in your browser. When you press the save button on the top your browser is triggered to let you save the edite
by codetrotter 4y ago
When you press save once, the changes are applied in your browser. When you press the save button on the top your browser is triggered to let you save the edited HTML to your computer.
Afaict, the edit and save is local and not sent to the server. So to persist changes and make them visible to others you’d need to then upload the edited HTML file to the server, using for example scp or sftp, or whatever method is used for deploying changes.
So for example you could put this in a git repo and have GitHub or Cloudflare Pages host it, and after you make an edit to a page from the browser you’d put the edited HTML file for the page in the git repo, commit that and push it to GitHub or whatever.
Seems pretty useful actually.
- indigodaddy 4y agoThanks for the explanation. That does seem useful indeed.
- rcfox 4y agoNot sure about Feather, but you can give TiddlyWiki a GitHub personal access token (saved in localstorage) to have the save button do a git commit automatically.
- hkt 4y agoS3 credentials and WebDAV are also options for tiddlywiki.