Hi Tobias. What I was originally trying to achieve was a reliable method of accessing my wikis from anywhere. I'd already read about the node.js deployment method, believed this method had a more robust foundation for storage and access (while still allowing the attractive save as a single file when beneficial) and had it running locally in minutes.
In retrospect those are the primary reasons I ended up with node.js hosted in the cloud. I wanted SSL for the obvious reasons and at the end of the day NGINX was pretty simply to deliver on that. The challenges, as is often the case, was the very specific combined syntax requirements of the NGINX config file (not to mention which of the various files) the tiddlywiki --server command including the paths necessary to support multiple wikis, and then the server config tiddler, which I'm wondering if it is part of TiddlyWeb or not. I was looking at TiddlyWeb. Initially didn't understand what it was. I looked to switch to it, as a more robust multi-user platform (right???), but found it was the original TiddlyWiki not TW5. I like the prospect of TW5. So, I wanted a reliable method of accessing wikis from anywhere. Node.js in the cloud delivered on this front. Then I decided I wanted to be able to edit it offline. I'm actually on a two day car trip right now. I thought of tools I used in the past like rsync but then wondered if perhaps OneDrive or Google Drive might offer a solution. I already use them both on my laptop. A quick search revealed the ability to mount Google Drive from Linux. With that done I now appear to have the ability to edit online or offline with offline changes done to Google drive syncing back on connect. You're correct about the potential conflicts, minimally in the server config tiddler save configuration (none/local vs. https://xyzwiki.domain/path/. However, currently I am only looking at a single user configuration, so I am just managing that tiddler manually with a startup script on the local version. It removes the config tiddler on startup, then puts it back on shutdown. I have not worked with this enough yet to know whether it is reliable. I can actually see other changes on switching between different clients and potentially local node.js servers being beneficial to change the theme/layout depending on the device, in particular my an Android phone. However, while I now have node.js on my phone ready to go, it doesn't look like offline access to Google Drive contents from the phone within node.js is going to be a "no brainer" like on the laptop. To your point making the cloud version read-only for sharing could provide benefit. I do indeed want to share some of the wikis in that fashion. They can even be encourage to save their own local copy I gather. However, I also want to be able to edit it via that server when I am on some foreign device with just a browser. I could start up two instances for this. So my desires in summary are: - Ability to access from any location or device (or as close to this as possible) - Ability to make offline changes that sync across all devices Future considerations/thoughts: - Multi-user collaboration on wikis - Versions/version control of individual tiddlers P.S. Is there a TW roadmap page somewhere? A page that includes the original and TW5 differences in terms of offshoot development and support - plugins, extensions, hosting options. Thanks very much. I appreciate any insight or advice on above. All the best. On Tuesday, December 27, 2016 at 7:13:17 AM UTC-5, Tobias Beer wrote: > > Hi Greg, > > Can you perhaps summarize what you're trying to achieve and how the > different services / components fit into the picture? > > What I would find interesting is an environment where you have different > node.js configurations whereas the web-facing env, perhaps AWS, would > provide read-only access only while the local server gave you read-write > privileges. Otherwise, if all endpoints provide the same read-write > capabilites, what auth process do you plan on using so as to protect your > web-faging server from visitors whom you don't want to grant write > privileges? > > Best wishes, > > Tobias. > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9b650e5b-a9a8-487e-ba49-a08b035b4cc2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
