Maybe it’s obvious from the blog post, but I just want to point out that Tiddlywiki saver works out of the box if it is served via WebDAV.

All you have to do is: install Nginx, enable WebDAV module, place the wiki.html file in the WebDAV directory.

I should have made this clearer. I'll update!

I was happy to find that because Sharepoint supports WebDAV, you can store and serve a Tiddlywiki file from a Sharepoint file store and saving it will Just Work, and permissions are handled via Sharepoint/AD. Works great for a company knowledge base.

Doesn't Sharepoint already include Wikis?

Yeah but you know, it’s pretty horrible.

I was chatting with a MS engineer a year or so back... the Sharepoint implementation they included was written by an intern. they didn't actually mean for it to be released and wish they could reverse that decision but apparently it got a lot of use. Its particularly painful because their customer base has been harping at them to fix the bloody thing so it behaves like a real wiki tool and they don't want to spend the resources on it.

Tiddlywiki is a real piece of gem. I use it with github saver on a single machine. It works great for me. No server setup, no additional cloud provider since I'm already on github and I think the github saver works on mobile too with the page added to homescreen. Not completely sure about the mobile bit as I mostly work with my work machine

Anyone know how to get the code in this article to work inside zsh? When I try to run the wiki executable, I get a command line error: "zsh: exec format error: ./wiki.com"

When I try it in bash, the server starts right up.

I remember this from using redbean for something a few months ago, it's a known limitation of that project. The redbean docs say to just do `bash -c './redbean.com -v'`. It also says they upstreamed patches but no more information; maybe it got merged and updating zsh would work? No idea tho.

https://redbean.dev/#usage

patched ca. zsh 5.8: https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841...

Seems to work! Thanks!

fOr all the effort put into tiddlywiki's, I'm surprised no one has come up with a standalone desktop application that works in the same way yet built upon Electron.

Isn't https://github.com/TiddlyWiki/TiddlyDesktop/releases/tag/v0.... enough?

Why Electron, can the same thing not be accomplished using the File System Access API or using Native Messaging from a browser extension? I doubt a majority of TiddlyWiki users are going to be happy if Electron suddenly becomes a requirement.

It wouldn't ever need to be a requirement, but I imagine there exist people who want to use TiddlyWiki and for whom installing an Electron app would be a more accessible on-ramp.

IIRC part of the original intent of redbean was that it would be used instead of redbean in cases where having a web browser as the frontend was appropriate.

And now to dockerize it and throw it on fly.io? :) I mean, why not..

Redbean and Fly are a really good fit. I wrote some notes on that a while ago - it worked exactly as you would expect: https://til.simonwillison.net/fly/redbean-on-fly

Thanks! I knew I had also looked at your article a few months ago but couldn’t find it! Been itching to mess with fly.io for something (don’t have a fly acct yet) so here’s my easyish chance!

Highly recommend fly.IO. I have stopped reaching for anything else. For go servers, I just copy their Go starter template and deploy it. It is the fastest way I’ve found to get a project up. You can immediately get into an iteration loop and build tests and even staging environments around it inside of a days worth of work.

What is fly.io ?

Is it actually faster / easier to ask that question here and wait for an answer from some random person, or to simply click the link and read the first few sentences on the site to answer your own question almost immediately?

I’m sure tptacek has some good summarizing paragraph or couple of sentences somewhere on some HN comment (to succinctly describe fly.imo)

I don’t know. For most other sites, I’d agree with you. But with fly.io, it might actually be better to ask here.

devil's advocate :

ok. I went to fly.io.

here's what it says.

"Deploy App Servers Close to Your Users

Run your full stack apps (and databases!) all over the world. No ops required. "

Now, what does that mean?

It means they're a PaaS (Platform-as-a-Service), but instead of hosting your webapp on one VPS in a Frankfurt datacenter, they replicate your webapp (and databases!) all over the world so that latency is as low as possible for your end users and there is not one SPoF (Single Point of Failure).

So they sense if your docker thingy has a db (could be any flavor of db?), and they figure out db replication across all the “edge nodes/firecracker thingies” thru deploy for your app?