@c thanks for this write up. I’ve been interested in setting up a wiki on TW for awhile, but felt like there were too many barriers for me. I didn’t look at the using GitHub to Save page you linked to yet, but am I reading this right, that if you have the token, you can edit and save from any browser?
@kordumb I just double checked it. You'll need to add the token in each browser in which you use your TW (otherwise it would be a security issue and anyone could modify your wiki on your behalf). The token is saved in the browser for future edits.
@c yeah that’s what I had meant, entering the token in each browser. That’s awesome. Thanks so much!
@c That's great. I haven't done it with Github yet but this will make it easy when I do, thanks!
@jack What are you doing to self-host yours presently then?
@c I edit it locally then rsync it to a server behind nginx. For a while I had it running via node and edited "live" on the server but after moving servers around I decided to "de-complicate" it :). Using the iPad more is making me re-think how I manage it.
@jack @c I've started another one that I'm thinking of putting online. Have you any info about how to make it read only? I don't like the idea of it being out there for anyone to edit.
@stefp There's a way to do it when running node so that only users logged in can edit. I've simplified things by just uploading the .html file and serving via a web server. It looks editable online that way, but saving doesn't actually do anything.
@jack Thanks. Just tried it that way and it seems to be working. It doesn't seem obvious at first. I've noticed some small differences between Firefox and Safari. I can't get the "save changes" button to appear in FF. It was a great relief to find out what it could do in Safari.
@stefp I haven't seen any public/online versions that allow anyone to save edits to your server (node might give you an option to if you wanted, but I haven't delved into it yet). All the public versions require some sort of account/authentication set up to actually save the TW. On the other hand, it's generally very easy for people to download your entire Wiki and save a copy, or to drag/drop Tiddlers from yours to theirs. In most cases, if they do make changes and attempt to save it, the browser will simply force a download of the entire wiki to their local computer without any changes to your hosted version.
@stefp I'd like to hear more about safari because i've found no way to save from there outside of running it via Node. I use the Timimi plugin with Firefox for local wikis
@jack The button has disappeared again. Very frustrating. There's a button in tools marked "save all" that will let you save an html snapshot if you hold it down. It seems to come and go. I'll try that Timimi plugin.
@c Thanks. I've been playing around with it tonight. I guess it's just a matter of not adding stuff that you wouldn't add on any other public platform.
@jack The server status button is doing that if you hold it down and let go. My mistake. It's a quick and easy way to get an html snapshot for uploading.
@jack I've set TW up with Github Pages last week, mostly following @c's post, and it works reasonably well in Safari, on macOS and iOS as well.
If you can ignore the occasional 409 errorsthat resolve themselves on the second or fifth try…