Thanks for the reminder. Here is how I use TiddlyServer
I suppose I forgot to mention this other level of abstraction that can be done with TiddlyServer. I already lean on this heavily, as when I go to the Tiddly Server address there is a list of Wikis listed like a table of contents and even folders (inc Virtual folders) and subfolders that I can browse to find anyone of a number of Wikis. Eg My Development folder opens to list multiple wikis under hostname:/development/ I also like the ability to have any singleFile Wiki backed up to a single folder with all other wikis. I just noted I need to clean this folder up because despite compression its now 10GB+ in size
Browser address ts.local
![ts.local.jpg](https://groups.google.com/group/tiddlywiki/attach/49d56a8361c62/ts.local.jpg?part=0.1&view=1)
Until recently I had to present TiddlyServer at myIPaddress:8081/ to address the other servers competing to appear at myIPaddress:
Since TiddlyServer now uses its own dedicated and movable IP Address and setting it to port 80 there is no need to provide the port number at all.
The point with the tips in my original post is I can now refer to the wikis as at the IP address 192.168.1.81 or the domain name ts.local and the location such as
http://ts.local/Development/EditFields.html at this location even on my desktop with all the other servers the same there, is no need for an alternate port number and not only could I host the example EditFields.html Development/EditFields.html from a totally different folder and use the same address (The advantage of TiddlyServer) but I could lift and shift the whole server to another computer without changing any links, weather I used
192.168.1.81/Development/EditFields.html or ts.local/Development/EditFields.html with a Domain Name server.
- This way of using TiddlyServer means I do not have to edit settings.json to simply add another wiki to be served by TiddlyServer, just add it to a folder already listed on tiddlyserver (or one of its children)
- Inspired by your point Arlen I created and added to settings.json the full path file name to home, a single file wiki
Given my Current Focus on TiddlyServer can I suggest these improvements?
- Add a automatic method to minimise the number of backups retained.
- Perhaps allow browsing the TiddlyServer tree at addresses such as
http://ts.local/Instances/
or http://ts.local/Instances
However in this second case, look to see if the folder contains index.html and load that if it exists, if not do the same as the first.
Currently if the address points to http://ts.local/WikiFolder
Then it loads the folder wiki
- I wonder if we could somehow configure redirects, to other urls under TiddlyServer, such as Node.js redirects, perhaps even allow them to be added to settings.json
Thus TiddlyServer could also act as directory to many resources (a Useful product on its own even)
Thanks for reminding us all of the power of TiddlyServer.
Is there something more to TiddlyDesktop I am not yet aware of?
Regards
Tony