Written in golang.
Also available for moka (see https://moka.pub)
In addition to local saving. It is also possible to publish to multiple servers at the same time.
I want to be sure I understand. This is simple a file-based HTTP server, correct? It lets the user serve files ( and folders as well?) over HTTP. Something like Node.js’s http-server or Python’s built-in http.server.
I see that there are specific routes for TiddlyWiki and for Moka. But I’m not sure if they do more than serve those static single-file wikis. Does it also serve as a saver so that you can save back your changes?
2 Likes
Yes. The instructions say how to set it up. Then you can upload content to the server.
Now. In addition to the golang version. I also developed a php version.
Also. Go through the edit-json part. There is a button to publish content to several servers at the same time on the browser side. If it happens that you are editing right on the server. Then it can be saved on your server as well as another backup server at the same time. And if it’s edited locally. Then it’s split into two parts. A button to save locally. One button publish to multiple servers.
This edit json function also generates a backup data per save.
This publish to multiple servers version doesn’t look like the data size can be too big. So it has to work with my tiddlywiki size reduction technique.
Hi @tomzheng thanks for sharing, this is very good to see. I encourage people to give it a try and explore the possibilities of this architecture.
1 Like