I understand the tiddlywiki plugin mechanism, and have recently written one myself. I don’t want to ask about that. What I’d like to know is whether there is any extension mechanism for the Node.js script “tiddlywiki”?
Or if not, is there some nice way to handle what I want to do?:
I’m writing a documentation wiki that will be served mostly in a read-only format. I’ve been editing it by running the Node version locally, pushing it to GitLab, and serving it through GitLab pages, using a read-only mode mostly borrowed from Mohammad Rahmani’s TW-Utiliy plugin. This workflow has been fine when I’m the only author. But there will soon be others, and I’d like to simplify it to run the Git integration from inside the wiki, if that’s possible.
Any suggestions for how to do so would be welcome. My thought was to integrate another action to the save-wiki
button that said something like “Push to Gitlab”, popped up an input for a commit message, and then passed that back to the server, so that it could do a push to GitLab. But that would involve the server knowing how to push to git, and I assume that’s not built in. (There are other open questions about auth, and so on, but if I can’t get the Node server to do this, then those aren’t worth pursuing.)
I have read Mohammad’s GitHub Saver tutorial, and I might look into that if this doesn’t work. But I really want the git granularity of separate tiddler files in the commits.
So, is there a way to add functionality to the tiddlywiki script without forking it? (This is absolutely not important enough for me to try a fork. Even if I weren’t too new at this, the other content writers are all competent git users, and we can work it out… although the StoryList will be a headache.)
Or is there another useful way to handle this so that the content is regularly checked into a shared git repo?