I know this will be a dumb question but does one sit it up? I am used to creating "web application" and running it on a web server of some sort: Apache / IIS /Lite. In this perspective the web server or what not handles a lot of the complexity, thread pools, isolation, restarting, logging etc etc. I frequently see applications like this that is "one binary" and you run it by starting it on the command line. That is e…
widdler is meant to be more of a private wiki. if you want to share a specific tiddlywiki with the world it's as easy as copying the html file to a webserver - it will then be static content (users can edit it locally, but the changes won't be sent back up to the server). My current use case is: running on a vps and exposing a password protected space for me to jot down various things.
At the very basic level you can SSH, and type in the command. Bobs your uncle. Then unless you something it shuts down when you end your session.
You can just set it to execute in the background with basic sh or something like tmux.
Or do you set it up in systemd to be watched and restarted if something goes wrong?