Saver options and combinations

#1

I find that I change out savers every few years because each of them solves unique problems but also has unique limitations. For a while I only used my work laptop, but now I’m running a personal laptop as well, and that changes the needs. I just went back through @twMat 's site SetUp (tiddlyspot.com) site to see if I saw anything new, but I’m not sure if it’s been updated very recently, so maybe there’s others out there now. It might just also be interesting for others to share their setups for people to get ideas.

My setup

  1. Machines:

    1. Primary: Work laptop - Windows, no admin access, got Node.js installed pre-lockdown, have SharePoint available (aspx/webdav), can get to github, but not save to it (it triggers corporate security alerts), use Edge browser
    2. Phone: Android (Samsung), use Firefox browser
    3. Home laptop (new) - Windows, has admin, can get to SharePoint (and everywhere else), use mostly Edge browser, some Firefox

  2. Current setup (5 different ones today):

    1. Primary organizer is on Node.js run in a OneDrive folder
      • Pros: Get per-tiddler infinite backups, can programmatically dump .tid files in that folder from other places that eventually get picked up. Saves are VERY fast which is important. Offline which is important as I’m often away from network during the day.
      • Cons: Can’t get to this wiki from either my phone or work laptop, which is now problematic as I want to use home laptop too.
    2. Team based one-to-many wikis for my work team are all using .aspx/webdav on SharePoint
      • Pros: Super easy to setup, can get to them on all 3 of my machines and my team can too
      • Cons: Not really capable for multi-user simultaneous-edit situations, doesn’t like to have very quick changes, so not good for high-change-volume situations like task management
    3. Team based co-authoring for my work team used BOB, but discontinued due to glitches
      • Pros: Great for heavy co-authoring / task management with the team, worked on corporate network and even remote partners could work through VPN
      • Cons: Struggles as we go from desk to meetings and flip back and forth on network types, ended up losing data and having other sync issues.
    4. Public stuff I use combination of aspx/webdav and github/tiddlyhost
      • While on my main work machine, saving to tiddlyhost / github triggers some security situation and they block the site. I’ve got away with having them unblock it temporarily, but this is not a good long term situation. Now I do most stuff locally, and then transfer to github/tiddlyhost only at the end when using home machine. This slows down plugin development considerably right now.

  3. Plan at current:

    1. Transfer my Node.js setup back over to the .aspx/webdav on SharePoint
      • Gain: Will be able to get to wiki from mobile and home machine again
      • Lose: Will lose per-tiddler backups and will probably have to turn auto-save off as even SharePoint gets confused with too many quick saves (which happens commonly with task management). This will lead to probable minor data loss.
    2. Leave all my work one-to-many wikis as .aspx/webdav, this works really well.
    3. Wait for the next generation of multi-user to re-introduce it to my team and hope it proves more stable than BOB did for me/us.

So I guess my only specific question might be if there’s a “folder-based” saving mechanism that I can setup easily that will allow access from my phone and home machines? Combining the file-per-tiddler part of Node.js that I like with ability to have access to it everywhere?

Anyone using Firebase?
#2

If you are able to set up Tailscale on the machine running the node.js wiki, you can access it from other devices. I have been using it recently both to access my node.js wikis remotely and my WebDAV wiki farm.

#3

Have you looked at the recent webDav server?

Also there may be a workaround using local storage or browser based solutions like couchDB IndexedDB - see IndexedDB Plugin by Andreas Abeck he actually says what you are saying;

This is quite useful if an application / plugin installation is not possible (we have quite some restrictions at work…).

Then there are portable apps and USB if they are available.

#4

Hmm looks like I’ll need to install software to get this working which I can’t do from my main/work machine, but it might be worth a try to go the other-way-around and “host” from home machine. That would kill my ability to access things offline during the bulk of the day though… worth an experiment at least though.

#5

Right, the machine running my wikis is both under my control and available 24/7.

#6

Thanks @TW_Tones,

Webdav: I haven’t, though my thought is around keeping a file-per-tiddler setup while accessing the same wiki on multiple devices. I had thought the WebDav options were single-file?
IndexedDB: I thought that these meant storing in the browser, which seems to mean that accessing the same wikis on multiple devices was out, but maybe I misunderstood?

#7

Sorry, I should have explained. If you can have a wiki and or tiddlers represented in a separate database you could theoretical save the DB to a file share (or USB) and reimport elsewhere. Basically convert it into data without an applications/executable and you may be able move that between your environments. Ie a database row per tiddler to a file per tiddler mechaisium.

All you want is effectively the tiddlers to move between environments.

I feel for your dilemma, being there before myself.

The one savings grace maybe you cant be in both places at once. So you can have a transfer trigger. Before closing in each location.