Announcing TiddlyServer 2.1 Stable

[Arlen Beiler]

Hello everyone, TiddlyServer 2.1 is finally here. I believe it's stable and I've gotten most of the bugs worked out. I specifically tested single-file saving (which I've gotten a lot of bug reports about lately) and I'm pleased to say that is working as well. Please continue making suggestions. I really appreciate your input. 

As usual, I forgot exactly one thing (why is it always one thing). The Readme in the release version says if upgrading from 2.0 you should run upgrade-settings.js. That might work, but it's probably better to just start fresh by copying example-settings.json and just copy and paste the tree property over from your old settings.json file. 

This page is the one you should follow for upgrading: https://arlen22.github.io/tiddlyserver/docs/gettingstarted.html

The release page is here: https://github.com/Arlen22/TiddlyServer/releases/tag/2.1.3. The rest of this is what I wrote on the release page. 

You might not see much difference on the surface, but underneath a lot has changed. A lot of the changes center around the server config and the tree specification, both of which have seriously improved. You still have to write JSON, but the error messages are quite a bit clearer, especially if you have valid JSON text, but an incorrect setting or property name.

The tree has been reworked to allow group and folder level customizations. We don't match the path on disk, but if you specify it in the tree you can customize the backup settings, specify which users can access the folder, and change the put saver settings for that part of the tree. We've also added index options for groups and folders, so you can customize the directory page.

The simple things are still there just like before.

• Serve and save single-file wikis. You can also disable this feature or restrict which users can use it.
• Serve and modify data folder wikis. Now with WebSocket support.
• Serve files and folders anywhere on disk and organize them into virtual folders (called groups).
• Did you know you can specify the path to a file directly in the tree? Any path can specify a file or folder, even as the root of the tree, but I don't know why you would serve one file.

The more advanced features include

• Cookie-based login, which replaces basic auth.
• Advanced routing tree customization, including access restrictions and index pages for groups.
• Flexible options to specify the IP addresses to bind to.
• Serving over HTTPS using the NodeJS HTTPS server implementation.

It's all in the docs, which now has a home. Check it out at https://arlen22.github.io/tiddlyserver/. They're definitely not comprehensive, so feel free to ask if you aren't sure about something.

A big thank you to every who has made suggestions and tested the betas. TiddlyServer may not be done yet, but it wouldn't be what it is without that feedback.

[Scott Kingery]

Hi Arlen,

Thanks for your work on this. I'm new to TiddlyServer but I have used node on windows. I am trying to figure out if my data folders should be under the webroot folder. Like webroot\mywiki. And if I was using a single html file wiki would that go inside webroot? Lastly, is it using a specific port?

Thanks

[Mark S.]

Just going by my own experience.

I believe you could put your single file wiki in "webroot". You could also put any data folders in a dir below "webroot" (e.g. webroot/mywiki) and they would be served up as data folder TW files. Mostly you can't put

a single file TW into a data folder and expect it to be visible (at least not automatically visible). The upshot is that you can serve up a bunch of single file TW and data folder TW's, and all

use the same address and port number. Any folder with a "tiddlywiki.info" file in it is served up as a data folder.

You set the port number down under bindinfo. Inside "bindinfo" you can put:

             "port": "8080",

to set the port.

Good luck!

[Mark S.]

I haven't tried it yet, but it seems like a lot of the information a user would need is missing. Like how to make "children" of trees. How to set the port, like Scott asked. What's the difference between a group and a folder? How to use those new https super powers?

Maybe just making a sample file with lots of different possibilities commented out would help.

I think TS is great, but it really needs some specifics to help people.

Thanks!

Mark

On Wednesday, September 4, 2019 at 2:47:01 PM UTC-7, Arlen Beiler wrote:

[Scott Kingery]

Ahha...solving my own problems. On the Getting Started page you wrote "create a webroot and a backups folder beside the TiddlyServer folder"

I read that as inside. That would mean the relative path ../webroot wouldn't work and ./webroot would be correct (2 dots vs 1 dot).  Makes much more sense now. 

I also read deeper into figure out how to use a port other than 8080.

[Mohammad Rahmani]

Hi Arlen

 Good improvement! Specially the documentation has got much better.

As Mark noted earlier, still the setup for newbies is a problem and I would recommend simpler fewer step to setup.

Thank you again for all your efforts and this useful and great piece of work..

Best wishes

Mohammad

--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSTHj3t-nSLR9-MgEnDUtKy23Ak25Y5ZSamZQoFm4ECq%2Bg%40mail.gmail.com.

[Scott Kingery]

I might be able to contribute some documentation when I get some more time.

Tonight I learned:

In the tree line of settings.json, even though my windows directory is ../apps/Work the settings file is expecting lowercase ../apps/work

For HTTPS, if you have the certs, you just have to learn where to put them and add some details to your settings.json. I wrote up some details awhile back on how to make your own certs on Windows when I was documenting how to get Node.js set up. https://techlifeweb.com/tiddlywiki/tw5tribalknowledge.html#Getting%20Started%20with%20Node.js%20on%20Windows

Scott

[TonyM]

Arlen,

Thanks so much for updating and improving your wonderful solution.

I will be upgrading shortly.

In the vanilla node version there are static tiddlers "path/#tiddlername" published at "path/tiddlername" will this be possible with TiddleyServer ?

Regards

Tony

[Arlen Beiler]

TiddlyServer hands all data folder requests off to the TiddlyWiki server instance, so it should function the same for core features. I believe the path may have been changed to /static/tiddlername in 5.1.20.

--

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 tiddlywiki+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1160940b-d57c-4013-b083-f600e4616556%40googlegroups.com.

[Arlen Beiler]

I added a simple tree example to the server config page and also linked to it from the getting started guide. I will add more information as I have time. Thank you for your suggestions. 

Arlen

--

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 tiddlywiki+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/91fca781-c70e-47a8-9d55-350d52f88d14%40googlegroups.com.

[mauloop]

Hi, Arlen.

I would like to upgrade the TW version included in TiddlyServer to 5.1.21, which fixes lot of 5.1.20 bugs. I think I could simply download the new TW5 rel from Github and replace the tidllywiki subfolder in the Tiddlyserver install dir.

I noticed that all of the plugins, themes, languages, as well as the core itself, provided with Tiddlyserver are packaged as bundles (the plugin.info files) that include the plugin metadata and all of the plugin tiddlers, while those coming from the official Github repo are made of folders containing many .tid files. I imagine that you choosed the bundle format due to some performance issues.

Is it correct? Should I care about this while upgrading TW5 rel? How can I repackage TW 5.1.21 as you do with the 5.1.20 included in Tiddlyserver?

Thanks in advance,

)+(

[Arlen Beiler]

Actually there is an easier way than replacing the folder. Just set _datafoldertarget property in settings.json to whatever folder you want to use. The plugins are bundled so they load faster. It doesn't matter, TiddlyWiki just loads them either way.

--

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 tiddlywiki+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/42630cef-8bb6-4100-b7c4-51b5e192e024%40googlegroups.com.

[mauloop]

Just set _datafoldertarget property in settings.json to whatever folder you want to use. 

Just tested. It works. Thanks. Really a great job.

)+(