TiddlyWiki on a Webserver

[Gabriel Jülke]

Hi everyone,

I'm trying to set up a TiddlyWiki on a Webserver right now but can't manage it to work... Atm I am trying out MiniTiddlyServer, but I am not shure which version I am using. I found it somewhere on the web and all "official" sites are down, also I can't find any howto or something like that. 

So the problem right now is, that i can start the mts and (at least it looks like) I can create a admin-user. But when I try to log in with this user, I can't. I tried and modified the access rights even to chmod 777 for all mts files... but nothing... does anyone has an idea or can give me a howto / instruction to set up a TiddlyWikiServer or how to use anything else to use TiddlyWiki serverside?

thanks

[Måns]

Hi Gabriel

TiddlySpace is a very good place to have your tiddlers.
However if all you want is to place your TW on your own server and be
able to save changes online - here's a quick way to do it:
Go to http://xn--mns-ula.dk/TWWEB/
Download the zip package
Extract files
Adjust usernames and passwords in store.php
Upload files to a directory on your server
Open your TW via http
Save changes via the backstage menu: "upload"

Cheers Måns Mårtensson

[PTP]

... does not work for me. I can't get to the backstage after I uploaded and opened the TW :-(
Any hint?

[Tobias Beer]

Hi PTP,

This recently revived discussion for MicroTiddlyServer may be of interest to you:

https://groups.google.com/forum/?fromgroups=#!topic/tiddlywikidev/5gqF4IvnU78

Then there's also store.php from BidiX (which is part of TiddlyHome)...

https://code.google.com/p/bidix/source/browse/trunk/TiddlyWiki/contributors/BidiX/serversides/UploadService/store.php?r=140

Best wishes,

— tb 

[Paro Parrot]

The MicroTiddlyServer sound easy - but did not work for me. After uploading the index.php and my TW I can see it, but cound'nt edit. Any hints?

--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/Q-U87Gol31c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/bdb59527-091e-42b5-9274-bf6ee5344ba6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tobias Beer]

Hi PTP,

I only ever used store.php and setting the right access / executable flags it works quite nice.

Here are some musings on making it work

http://tiddlywiki.org/#UploadPlugin

As for MicroTiddlyServer, better ask in the other thread.

— tb

[Måns]

Hi Tobias and PTP

http://tiddlywiki.bidix.info/ doesn't exist anymore.... That's why I uploaded a zip file with store.php in the second post...

PTP If you use TWC you'll need UploadPlugin and PassWordPlugin. You'll get those plugins automatically if you create a site on tiddlyspot.com.

When you have a tw on tiddlyspot.com you can download it and upload it to your webserver/ftp (via the backstage) and make it save itself with store.php.

You'll have to write the correct URLs, username and password. (Which you set up in the store.php file.).

 - If you use TW5 you don't need any plugins but you still have to write the correct URLs, username and password. (Which you set up in the store.php file)

Here are a couple of examples:

TWC:

TW5

Cheers Måns Mårtensson

[Tony Grosinger]

I would highly recommend looking into running TiddlyWiki on Node.js. I tried using store.php, however I think running it through node is much better. I am also proxying that through apache to add SSL. Seems the most stable configuration that I have tried so far.

[Tobias Beer]

Hi Tony,

 

I would highly recommend looking into running TiddlyWiki on Node.js. I tried using store.php, however I think running it through node is much better. I am also proxying that through apache to add SSL. Seems the most stable configuration that I have tried so far.

I added the below here: Hosting Via node.js Or store.php? @ tb5:

Those are two entirely different modes to operate...

1. node.js (=> pro)
• requires a node capable server => not so common, tends to be more pricey when commercial
  
• on top, needs to install and admin TiddlyWiki for node and possibly other npm packages on the server
• operates on a per-tiddler basis
• authentication?
• should possibly be called "experimental" => use with mucho care-o (whatever that means)
• backups?
2. store.php (=> simple)
• requires "just" php => very common, plenty of affordable or free options
• nothing more to set up in terms of TiddlyWiki, at all
• operates on a per wiki basis
• basic autentication
• tried and tested since 2008
• does backups

Between the two, right now, there's really just one option I would use.

What I actually do right now for tb5 is...

3. node.js + standalone (=> best of both?)

• requirest just the basic, cheapest of hosting, plenty-o-free
• github pages is just fine for me atm
• node and TiddlyWiki are installed on your local machine and so you have full controll
• you can organize and edit on a per tiddler basis, but node bakes full standalone wikis
• no authentication needed
• fail-proof and most secure, no writing to any server-store via web, be it node or file => just basic FTP
• manage backups however you want, e.g. github

Unlike the other two above, this does not allow any editing over the web.

But then, you can always edit your contents, preview changes and temporarily store them, say, in a trello or actually edit tiddlers in GitHub which we already do with documentation for http://tiddlywiki.com, of course having to then merge things at some end.

Best wishes,

— tb

[Jeremy Ruston]

Hi Tobias

• should possibly be called "experimental" => use with mucho care-o

I don’t think that’s quite right. I and other people use TiddlyWiki under Node.js every day. I think that the issue is that we don’t have all the parts for multi-user editing, but that’s not quite the same as saying that it’s an experimental configuration.

• backups?

With the Node.js configuration, Git is a pretty handy way of managing backups.

Best wishes

Jeremy

1. store.php
• requires "just" php => very common, plenty of free options

• operates on a per wiki basis
• basic autentication

• does backups

Right now, to me, there's really just one option I would use.

Best wishes,

— tb

 

--
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 post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/bf22bc61-20e4-49e7-9ed0-c4c560dfe537%40googlegroups.com.

[Tobias Beer]

Hi Jeremy,

 

I don’t think that’s quite right. I and other people use TiddlyWiki under Node.js every day. I think that the issue is that we don’t have all the parts for multi-user editing, but that’s not quite the same as saying that it’s an experimental configuration.

I do too. However, using TiddlyWiki with node.js and running it on a server that is not serving on localhost are two separate things, to me. Running it on a remote host sure is not the most straight forward thing for anyone who isn't a web-developer or -admin of sorts. Making sure noone can tamper with that node instance or just a wiki being served with it syncing changes back via the tiddlyweb plugin, how is that done safely?

Multi-user is an issue I have deliberately left out of the picture as mostly GNA, generally not available.

With the Node.js configuration, Git is a pretty handy way of managing backups.

Dito, on a local machine that's comparably easy to set up and manage.

On a remote server, not quite as simple... unless you have some deploy script.

Best wishes,

— tb