If I understand correctly the problem you are having is saving the 
tiddlywiki when you edit it. 
But it is accessible to the people you want to access it.

If this is the case the responses in this thread do address your problem, 
but we probably have not been specific enough with instructions.
None of the options are immediately obvious, we are currently putting a lot 
of effort into documenting them and creating tools to make this all easier.
I am planning on making a similar setup on my home server once I get a real 
internet connection, unfortunately the installation got cancelled due to 
the quarantine in France, so I am not sure when that is going to happen. 
When it does I will be sure to post any tools I make on here.

Single File Wikis

There are browser restrictions that prevent any type of saving other than 
downloading the modified file unless you have some sort of external helper, 
there are many options for this. One is a WebDAV saver that you can have in 
the wikis you are sharing and it can make saving not require any further 
effort on the part of the people editing it, assuming they can access 
webdav mounted file systems, this should be possible on any desktop 
operating system, I am not sure about phones/tablets.
I do not know the details of setting up the WebDAV saver, I believe Mario 
may be one of the local experts on that.

If the people using the wiki have the next cloud folders with the wikis 
syncing on their computers there are a number of options for savers. On 
tiddlywiki.com in the GettingStarted tiddler there is a big list of savers, 
it is confusing, we are working on it, the ones that are most relevant to 
what you are doing if everyone editing the wiki has the folder syncing with 
next cloud are TiddlyFox, tiddlyie, Timimi and the Ruby server depending on 
what browser you are using and what you are comfortable setting up.

One thing to be aware of is that when saving single file wikis one person 
saving the wiki can overwrite another persons changes, so you have to be 
very careful when having single file wikis in a multi-user environment, 
there has been discussion about different ways to handle this problem, to 
my knowledge there isn't any definitive answer past 'be very careful'.

Node Wikis

If you want to use Node as the server be aware that you will need to do 
something so that the wiki server is also accessible from the outside 
world, and that you should put some sort of security layer on it. We do not 
have any standard setup for making a wiki accessible to the outside world, 
my solution was to make a custom express server with proper authentication 
and security on it and connect that to a dynamic dns provider and use it as 
a proxy to connect to the wiki, but that is not a straight-forward process 
and I don't have usable documentation for it.

If the above isn't enough to get you started with the process of getting a 
server set up that is accessible to the outside world I suggest using one 
of the single file wiki methods, currently setting up a secure multiuser 
node server that is accessible online isn't a simple process. I am working 
on updating the server I made to do this, but it may be a while before I 
make any significant progress on it.

-- 
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/05f3004b-7e4e-48bd-b9ad-e2f505b712c3%40googlegroups.com.

Reply via email to