TiddlyServer 1.0.0

[Matthew Lauber]

All, 

     After far too long, I'm ready to release TiddlyServer 1.0.  TiddlyServer is a special purpose Desktop app, designed to facilitate managing multiple instances of TiddlyWiki running as a server.  It does not require internet acess to access the wikis.

TiddlyServer can import both TiddlyWiki files and TiddlyFolder wikis.  For each wiki, you specify a prefix to serve it with and the source to import from.  It will copy the wikis to its own internal store and begin serving them up at http://localhost:8080/{prefix}/.  The export button for each wiki will convert it to a single file wiki.  It can be installed from https://github.com/mklauber/TiddlyServer/releases/

[Handoko Suwono]

Great to know there is another Tiddly in the world of TW. My rough question is how does it relate to TiddlyDesktop? https://github.com/Jermolene/TiddlyDesktop

I read it somewhere (can't find it again) that Jeremy is stopping update on TiddlyDesktop. Just wondering how true it is or let the community self doing updates on TiddlyDesktop.

handoko -

[Mat]

This sounds big! Applause for Matthew!!!!

I'd guess I'm not the only one with limited experience of administering server software, so if anyone would be so kind and just explain what this actually enables? I thought the main point with a server was that it serves stuff over the internet (but then the same can be said of a html-page, and then look at TW). Like Handoko, I'm wondering how this differs from TiddlyDesktop? But also more generally, what other things could a server potentially do with/for TWs? Would it, for example and assuming it was hosted on some web hotel, let you have your own TiddlySpot type service?

Again, thanks for sharing Matthew!

<:-)

[Matthew Lauber]

This is intended as a replacement for TiddlyDesktop.  Jeremy at one point mentioned he was stopping updates on TiddlyDesktop.  His reasoning was that a lot of the feature requests for TiddlyDesktop were features built into browsers, like spellcheck, tabs, search.  As a suggestion, he wanted something that was more of a UI frontend to running tiddlywiki as a server.  Taking that idea an running with it, I decided to produce TiddlyServer.  It's designed as a nw.js application, where a native application is used to manage a variety of instances of tiddlywiki server.  A proxy server in front hosts each instance at it's own 127.0.0.1:8080/{prefix}/ address.  Hope that helps.

Matthew

[Matthew Lauber]

This is actually meant as a replacement for TiddlyDesktop, rather than as actual server software.  It's a UI frontend to running multiple copies of tiddlywiki, that simplifies and hides a lot of the complexity of using the server version of tiddlywiki.  It is not actually designed to serve things over the internet, only to you local machine.  As I mentioned to Handoko, I designed this as a replacement for TiddlyDesktop, based on comments from Jeremy about where he'd like to take TiddlyDesktop.  

One thing this enables is the ability to create links between wikis.  Because all the different wikis are started when TiddlyServer starts, a wiki available at 127.0.0.1:8080/example1 can link to a given tiddler in a completely separate wiki, available at 127.0.0.1:8080/example2. In the traditional wikifile version of this, browsers generally don't allow linking to files on the local filesystem.  

Another thing this can enable is the use of TWederation between you own wikis.  Because each one is running in server mode, and has it's own (locally) unique address, you can use TWederation to share tiddlers between wikis similar to how you could import them if you had an instance of a plugin library somewhere.  So this gives you the ability to test bed TWederation, which could certainly be useful as we continue to explore how to use the amazing work Jed has done to get wikis able to communicate.

I hope that helps to clarify things.  In retrospect, I've been so heads down on this project I forgot to explain exactly what I was trying to achieve and why.

Matt 

[Jed Carty]

It looks like a lot has happened while I haven't been paying enough attention! I need to add this to my growing list of things to look into more.

[Jed Carty]

This is great! But I can't get it to work on my mac. It works exactly like it should in linux but on mac the window that opens up just has NW.JS written in the middle and the menus just have the generic window manager options. I am not really familiar enough with a mac to know what is going on there.

But this looks like it will be extremely useful for me if for no other reason than I am horribly disorganized and this will let me list all the wikis in one place.

[Jed Carty]

Or maybe I spoke too soon, importing an html file still gives me an empty wiki, but importing from a folder works the way it should. I should probably put this stuff on github instead of here.

Still, I expect this will be very useful for me. This is one place where even if the only thing added is the convenience part it is still worth a lot.

[Matthew Lauber]

Oh dear. I don't have a Mac, so debugging that will take me a little while, but it sounds like a packaging issue on my part. I'll try to take a look at it next week, when I can probably borrow someone's Mac in the office.

[Jed Carty]

Where are the wikis saved? I was expecting some folder in ~/home but I can't find them saved anywhere.

[Matthew Lauber]

By default, in ~/.config/TiddlyServer/Default/wikis

[David Gifford]

I figured out how to import a file. But how do I open it? Hovering over the title of the file I imported shows me an insert text cursor rather than a cursor to click a button, but then when I click the title of the file it opens firefox to localhost:8080/toodoo (toodoo is the prefix I gave the file). But then I get the spinning wheel for an empty tab saying connecting, and nothing else happens.

Dave

[Matthew Lauber]

That's very strange, you did everything right. It's the file unusually large or customized or anything? Does the same thing happen if you try importing a copy of the empty tiddlywiki from tiddlywiki.com?

[David Gifford]

yeah same thing happens with tiddlywiki.html

[Matthew Lauber]

What OS are you on?

[David Gifford]

Windows 10, 64

On Saturday, December 3, 2016 at 10:12:30 AM UTC-6, Matthew Lauber wrote:

What OS are you on?

[Matthew Lauber]

I'll check it out.

[Matthew Lauber]

Where was the file you were importing located?

[Gustav Wikström]

Hi, I just tried TiddlyServer as well and can report the same issue as the one David Gifford experienced.

Tiddlers have been published at different places on the harddrive. As an example; Tried to put them in a subfolder from the installation-path (C:/Temp/TiddlyServer/) and in a folder next to it. Tried both folder and file options.

I can go to http://localhost:8080 in the browser and it shows a list of available wikis, but using the links (which leads to http://loclhost:8080/whatever-chosen-path) just leaves the browser hanging.

Windows 10 64bit.

Kind regards

Gustav

[Matthew Lauber]

That's very strange.  I'll open a bug report, and try to figure out what's happening.  My primary machine is linux, so it'll have to wait until I get a chance to try it on a windows box.  

i'm guessing that the nodejs process is hanging, leaving the connection open but without data.  If you run C;/Temp/TiddlyServer/nw in the command line, do you get any output?

Matt

[Gustav Wikström]

I get the GUI-client up and running and the same thing happens when I go to the localhost-path in the browser. I.e. just typing in localhost-path:port gives the index of available tiddlers but clicking on one of the links (or clicking on the respective tiddler in the GUI) leaves the browser hanging.

 

Regards 

Gustav

[Ed]

Hi Dave, Hi Matthew,


I just experienced the samething as (you) Dave. By accident I found out the clicking on the words opened the file in the browser.
Well not really as localhost:8080/myprefix was indeed kept to a spinning wheel inside the tab. I waited a considerable time but
to no avail. Then I went researching this thread and found Dave's remarks and others who experinced the same.

Hope that this can be remediated in the future. Oh, btw I you could find the time to make readme file explaing stuff, that would
be great for people like me.. In laymen's term e.g. why the prefix is needed.

So keep up the good work Matthew! Again thanks, man!!
Cheers! Edm.
.
.


Op zaterdag 3 december 2016 15:39:33 UTC+1 schreef David Gifford: