3 ms·
So it’s a bit scary that I could press edit and appear to be able to edit the Feather Wiki landing page? Would it have required auth if I tried to save changes
by indigodaddy 4y ago
So it’s a bit scary that I could press edit and appear to be able to edit the Feather Wiki landing page? Would it have required auth if I tried to save changes? If not can you put basic http auth in front? I suppose the idea is to just use it locally and then publish any resultant http page and/or updates/edits to a static host?
- codetrotter 4y agoWhen 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.
- Infernal 4y agoRather than downvote I’ll explain - when you hit save you are given an HTML file with the page as edited. It is not edited in place.
- indigodaddy 4y agoInteresting ok, thank you.
- Saris 4y agoWhen you save it you're only saving a local copy, the server is unaffected.