Jed! Thanks for chiming in with responses.
On Sunday, October 20, 2019 at 4:51:23 PM UTC-4, Jed Carty wrote: > > > 1 - I haven't seen any. Eventually I my get around to making something. > The included TiddlyWiki itself is pretty helpful and seems it would be the ideal place for more documentation. (Though a YouTube tutorial or an export of documentation to a standalone TW would always be welcome.) For what that's worth. ;) > 2 - If you set 'suppressBrowser' to true in settings.json it will not try > to open up the browser automatically. See here: > https://github.com/OokTech/TW5-Bob/blob/master/Configuration.md > Perfect! Thanks for the detailed list of values, as well — which led into my next question .,.. > 3 - You can set the location of everything but the root wiki by setting > the wikisPath setting in the configuration > > 3a - Be careful about syncing the tiddlers, you can have Bob and the > syncing fight over changes to tiddlers. And if you have multiple Bob > instances editing the same wiki and syncing going on it can get worse. > > 4 - I don't know about best, but I periodically zip the full wikis folder. > Eventually I will get around to making an automated back-up for Bob. > Good point about the conflict with the */Wikis* files themselves. For now, I think my backup strategy is going to be working outside of the cloud folder, then syncing my whole Bob folder (minus the *.exe*) to a subfolder in the cloud folder. Long-term, an internal backup mechanism for individual tiddlers (allowing the user to roll back, perhaps from the BobHub) would be *awesome*. But so would an edition that comes with free ice cream. ;) Writing some kind of management for such a backup would be a project of its own, I imagine. 5 - .meta files are created by the core server. They are created for any > tiddler that isn't a normal .tid file, like images > Huh. Any idea what they actually *do*? > 6 - The readme has an incomplete list of features that I think can be > improvements in the contexts where I use tiddlywiki > The possibilities for sharing, bundling, and trimming are certainly intriguing. Also the possibilities for collaboration on the local network (which I may never get to take advantage of, but they're still intriguiing!) ======== At the moment, I'm still working on getting a TiddlyWiki's worth of tiddlers *into* a new Bob wiki. I've been breaking down my imports into small .JSON bundles to find which tiddler(s) is causing the problem, but at some point, Bob crashes out, and I'm left with a broken wiki. I've tried deleting the imported tiddlers manually, but that doesn't seem to help, and the tiddlywiki.info doesnt seem to have changed since it was created. Not sure there's anything else I *can* roll back to the pre-broken state. So, for the moment, I'm just creating new BobWikis and importing Big-JSON-block-that-works then smaller-JSON-block-that-breaks-it, trying to figure out what in my existing tiddlers is throwing a spanner into the works. -- 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/4542605f-fb5a-49a3-8015-aa2303c13966%40googlegroups.com.
