Update to TiddlyServer 2.1 Beta

142 views
Skip to first unread message

Arlen Beiler

unread,
Aug 2, 2019, 4:40:10 PM8/2/19
to TiddlyWiki
Hi TiddlyServer testers,


Here is an update to TiddlyServer 2.1 Beta. The simplified tree format from 2.0 is back, but the expanded format is available. A string represents a folder element and an object with no $element property represents a group element. 

You can use this for a basic settings.json file

{
    "tree": "../webroot",
    "bindInfo": {"bindAddress": ["127.0.0.1"]},
    "$schema": "./settings-2-1.schema.json"
}

Backup your current settings.json and don't depend on upgrade-settings.js at this point. I will update that soon.

Let me know if you run into any problems.

Here's the link again. 


Arlen

Arlen Beiler

unread,
Aug 2, 2019, 4:41:47 PM8/2/19
to TiddlyWiki
And then I forgot to push the last bit. So here's the updated link.


Enjoy!

Arlen

TonyM

unread,
Aug 2, 2019, 6:28:19 PM8/2/19
to TiddlyWiki
Arlen,

Thanks for your work, I should be able to test Sunday Sydney time.,

Regards
Tony

Mark S.

unread,
Aug 2, 2019, 7:29:58 PM8/2/19
to TiddlyWiki
Hello Arlen,

What are the differences between the two links you provided? They seem to lead to the same place ??

It looks like single-file wikis are now correctly indicating their "save" state -- great!

In terms of documentation ... if I didn't already have a settings.json file, I would be totally lost. There's no
place that tells you how to set the port. There's no example of trees and sub-trees (children?). I think most
first-timers aren't going to know where to use $element and how to create more "roots" and branches.

The format for TS 2.0.14 was easy to understand, but I find TS 2.1 confusing. Presumably the complexity brings some new abilities?
Or is this required for the new node JSON parser? I noticed that Bob also had an uptick in configuration complexity.

I'm curious what the new features in 2.1 are. It looks very similar to 2.0.14.

There's a visual distraction problem where missing branches have no icon. See image below.

Thanks!

Arlen Beiler

unread,
Aug 3, 2019, 5:30:51 PM8/3/19
to TiddlyWiki
Thank you. Keep the feedback and suggestions coming. It helps me to know what features to add and what problems need to be solved. 

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/cca16cdf-7ae3-4486-8045-1fe5f65610bb%40googlegroups.com.

TonyM

unread,
Aug 3, 2019, 10:34:44 PM8/3/19
to TiddlyWiki
Arelen,

I raised an issue in GitHub but I have the new version running. 

  • With Version 5.1.20 Coming out soon (maybe). Can we upgrade TiddlyServer using the normal node tiddlywiki upgrade?
  • Is there documentation I can't find that can tell me about the use of the login process?
By the way I found it very useful to add another IP address on my windows machine and host TiddlyServer on that. It takes the default port 80 and does not interfere with any other server on my computer.

Thanks heaps
Tony

Regards
Tony
To unsubscribe from this group and stop receiving emails from it, send an email to tiddl...@googlegroups.com.

Arlen Beiler

unread,
Aug 5, 2019, 9:16:26 AM8/5/19
to TiddlyWiki
The static tiddlers are still experimental and the path may change in 5.1.20. TiddlyServer keeps it's own copy of TiddlyWiki to guarentee compatibility, but I usually try to upgrade to each new release fairly quickly. I will probably update 2.0 as well this time since 2.1 is not ready yet.


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/280067c2-38fc-4a25-bf3c-9b734efcb061%40googlegroups.com.

Arlen Beiler

unread,
Aug 9, 2019, 4:43:29 PM8/9/19
to TiddlyWiki
I'm not going to release any particulars on the login until I release 2.1 because I'm still working on it. I'm going to use cookie authentication instead of basic auth, so it will be a little more secure over unencrypted HTTP because the password is hashed with a PBKDF first. So keep using it like you have been for now and let me know if anything breaks. I'll add the basic auth back in for now. I'll let you know when I do that. 
Reply all
Reply to author
Forward
0 new messages