New TiddlyWiki user here.
First of all: thanks for this!
I thought I’d never find something like TiddlyWiki.
So nice to have a tool which doesn’t jail you into a certain infrastructure, platform or programming language…a low-code unhosted backend.
I’m using it as my personal notebook now, and am baffled how powerful & scriptable this app is.
Of course many of us will not be able to make use of your solution be cause we are dummies. If you can package or make executables all the better, although I am sure some of us can make use of it.
Hm…your server says “Payload Too Large” (maybe because of images inside the tiddlywiki).
I guess you have to change the uploadlimit (./redbean.com -D . -M 5000000) to something higher (add some zeros to 500000).
I and I expect others have had some spam appear in talk.tiddlywiki.org which are quickly flagged and removed from view. We need to be aware people or robots have joined to spam and possibly phish so we do need to be carful.
This illustrates the value in macro solutions without exe’s or Javascript because they are safer and harder to hide payloads.
Hang on @pmario and @TW_Tones! It’s not at all welcoming to new posters to make posts that question their motives.
There’s nothing wrong or suspicious here. @coderofsalvation is using Readbean which is widely used and extensively tested.
@pmario is correct that people should be careful running these low level commands, but it’s very important to make clear that that is general advice, and not specific to this case.
@TW_Tones this is absolutely nothing to do with spam, and bringing it up here just looks incredibly unwelcoming.
Please be aware that your words have an impact on people; @coderofsalvation is a human being, and doesn’t deserve to be treated with suspicion like this.
Would you be amenable to the title of the thread being changed to include a reference to a redbean server implementation? The motive is to make it easier for other interested users to find your post in the future.
@jeremyruston@ pmario @ TW_Tones thanks for the heads up, all good, no harm done
@saqimtiaz sure, I’ve updated the thread title as you request.
Btw. I don’t know too much about HTTP COPY & WebDav.
So I think I’ll just leave it at this simple reference implementation, and leave it up to somebody else to extend it further.
I know Rick’s Post thx, in fact, I simply summarized (+bugfixed) Rick’s post into a shellscript.
The zip/binary was posted on @ TW_Tones’s request.
@coderofsalvation … I’m sorry if it came through, as if it was “questioning the motives”. That wasn’t in my interest. … I wanted to make sure, that users know, that the commands in my post are dangerous if they are used “blindly”. … That’s it.
Yes, the topic deserves more attention and a more in depth write up.
Yes it allows saving.
redbean is a server that is scriptable in the Lua language. Assets can be embeded, served, and updated within the executable, or assets can be served from files on disc.
Assets (html, images, server scripts) are added to the redbean executable using the ubiquitous zip utility.
Unfortunately, the function (StoreAsset) which updates an asset in the executable is not yet working on the Windows platform. redbean is a cross-platform executable - meaning the exact same binary can run on Windows, Linux, and Mac - so build once, run anywhere.
One obvious possible use of redbean is distributing a tiddlywiki as a single-file executable.
This version of the server script is serving a tiddlywiki .html file from disk, and allows saving to disc without extra plugins for the wiki.
This is in my view very important especially with a view to finding a solution similar to Make TiddlyWiki your own - discussion. Basicaly finding a way to give people a simple download and serve with one or more tiddlywiki editions therein.
There is a solution called twexe which comes with a default wiki, and you can load another wiki and the distribute that, however we do need to find away to give it a crc check or something.
Thanks @coderofsalvation for introducing this alternative and making the exe, if you can think of any other ease of acquisition steps for the distribution of tiddlywiki “applications” do let us know.
It will be a few more days before I can give this the focus I want.
This is needed to turn off caching.
Reason: I’ve started to use a (redbean) tiddlywiki on my (and my wife’s) smartphone (using chrome’s ‘add to homescreen’) so we could easily share ideas for home refurbishment, holidays etc (using the ‘refresh all’-button).
However, it didn’t properly refresh new tiddlers because of caching.
In the browser network console, I could see it was doing a PUT request, while the server was not reporting any request.
(As if an internal http-request layer inside tiddlywiki was not relaying it)
If you include a .init.lua file which is executed first, you can set these options there and avoid the command line options, as well as do other initializations like setting the server address and port, or launching your browser if you like.
Good News i think
Mozilla are embracing and extending Justine Tunney’s brilliant work that underlies the terrific redbean project.
“Our goal is to make open LLMs much more accessible to both developers and end users. We’re doing that by combining llama.cpp with Cosmopolitan Libc into one framework that collapses all the complexity of LLMs down to a single-file executable (called a “llamafile”) that runs locally on most computers, with no installation.”
