Bob is a node-based server for TW that can run multiple wikis at a time and allow mult-user access. It can also save single-file wikis
https://github.com/OokTech/TW5-Bob Here's another approach to saving. When your copy of TW saves numbered copies of your file into your browsers download directory, it's using the default save mechanism. This mechanism works pretty much with any browser, making it the most universal save solution. The problem is that the name and location of the saved file is not convenient. The Polly project runs a PS* script in the background that can find and copy your version in the download directory back to it's original location. One idea is that the script could be enhanced at some point to allow sub-scripts to be run. These scripts could do something like a git pull on your TW's directory. That way your local and cloud (github) versions would be kept in synch. Unfortunately, Polly hasn't grabbed a lot of attention, so I just work on it when there seems to be a need: https://github.com/Marxsal/polly/ * PS is powershell, which runs on Windows, Linux, and Mac --------------- There are some 20+ solutions to saving listed at TiddlyWiki.com. Another possibility for GH and TW is to put your GH folder below the downloads directory. Then use PMarios' file-backups extension to save your file. From time to time you would need to commit and push your saved file. Another possibility is to use the local storage saver in conjunction with the GH saver. In this configuration, TW is constantly saving itself to the browser's storage without having to press the save button. When you press the save button, the file gets pushed to GH. You can then periodically do a pull to upate your local copy. In the event that you have a net disconnection, turn off the GH saver and save a local copy (in this case, setting the browser to ask where you want to save might be a good thing). Local browser can be confusing, at least it was for me. Jeremy warns us that the browser could cleanse it's internal cache. So far no one has reported that event. Then again, I'm not sure whether many are using it. But used in conjunction with GH the loss of an internal cache might not be a total disaster. I'm relating this as best as I can from memory, since I only played with local storage/GH for a short time a couple weeks ago. On Saturday, April 25, 2020 at 9:48:36 AM UTC-7, ludwa6 wrote: > > Thanks for the good explainer, Jed; clarifies some things i've been > wondering about. > > As to documentation, i'm still pretty fuzzy (still finding my way around > the many granular pieces at tiddlywiki.com) but would like to know: what > is this "Bobs" of which you speak? > > On Saturday, April 25, 2020 at 5:30:17 PM UTC+1, Jed Carty wrote: >> >> ludwa6, >> >> In a browser it isn't possible to save things the way you are talking >> about without some external help, like the browser plugins discussed on >> tiddlywiki.com. These are restrictions built into browsers and we can't >> change them. The way around them is to make a new browser, which is >> essentially what tiddlydesktop is, or to use one of the non-git or >> tiddlyspot savers that saves locally. Unfortunately the only thing that >> works out of the box without any other installation is saving on remote >> servers. I could say a lot about this but it would take a long time and be >> about 90% profanity. >> >> As far as the documentation goes, I am probably the wrong person to write >> that, but a GitHub issue would probably get some discussion and results. I >> have learned that there is almost no overlap in the documentation that I >> find useful and what most other people seem to find useful, if the >> reactions to Bobs documentation are any indication. >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3362dd94-ce6e-4490-a7c0-e7e66e20339f%40googlegroups.com.
