Different people will have different ideas and perspectives. I find it simplifies things to only use single file wikis. So that rules out node.js, but you can still use tiddlyserver. I found the problem with termux is that my Android kept seeing it as a non-running app and closing the process. But others have had more luck.
So anyway, I find a good arrangement is to use tiddlyserver, timimi or tiddlydesktop on the desktop, tiddloid (or maybe Quinoid) on the Android, and syncthing to synchronize the devices. At one time we were able to use file-backups extension on Firefox on the android, but firefox, in it's bid to make itself ever less useful, has nixed that option for the present. Another synch option is to use Google drive. The complication there is that the only way I've found to synch Linux is with rclone, which needs to be done manually (well, someone could probably write a cron script or something). The git saver works well, but of course you have to be online in order to save. Some people these days always are online (have a good mobile data account), so if that's you then it might be the simplest solution. The main thing is to turn off auto-save, because rapid-fire saves produces a 409 error. On Tuesday, January 12, 2021 at 1:12:22 PM UTC-8 [email protected] wrote: > Hey, > > I'm new to TiddlyWiki and as stated on the website there are several > methods to save and edit a TiddlyWiki. This is a bit overwhelming at the > beginning :) > > It seems that the choice depends on the individual use case, so I thought > I will share my use case and it would be awesome if someone could give me a > recommendation: > > * Multiple devices: Linux, Android and maybe Windows > * Synchronisation across devices > * Backup and History > * I am a geek, so terminal and server stuff should not be a big problem > * Only personal Wiki and no public or collaboration wiki > * Stable solution > > For me it seems that the 3 best options are: > * Node.js: Running a Node.js Server in the background on Linux and on > Android (Termux) and doing the backup and synchronisation with a cloud > provider (e.g. Nextcloud) > * TiddlyServer: same as with Node.js? > * Git Service Saver: I'm familiar with git and could imagine > buying/running a Gitlab or Gitea Server, but I'm not sure how practical > and stable it is compared to the other options? > > Thanks > > > > > -- 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/223fc2a4-3abc-44e3-96d9-10b186deb4adn%40googlegroups.com.
