Publicly hosting a read-only tiddlywiki where tiddlers are served individually?

[Kalcifer Kandari]

I'm working on a wiki and want to publish it read-only under my own domain name using a web host (nearlyfreespeech.net) rather than GitHub pages or similar, mainly because I don't like TOS such as this:

You agree that you will not under any circumstances upload, post, host, or transmit any content that:  

• is or contains sexually obscene content

The wiki isn't necessarily explicit in nature, but I don't want to censor information on it.

The wiki will be quite large and as I understand, using a single '.html' file will result in the entire thing being served to visitors, which is bandwidth inefficient and I don't want it to slow the larger it gets.

So are there any options to publicly host a read-only tiddlywiki where tiddlers are served individually, while preferably keeping features like search? I have heard about the node.js server and static html files, but nothing that specifically mentions public hosting on a web server.

[TonyM]

Kalcifer,

The best solution varies due to a number of factors. You can have a lot of text and interactions in a tiddlywiki without it being too big. Using the loading splash screen can stop people abandoning your site before it fully loads then it is in the browser cache and memory and performs well, even better than other sites.

The main reason tiddlywikis get ovesized is media, such as images and these can be externalised and loaded on demand.

Using noteself, rather than read only, keeps your hosted copy readonly but allows the visitor to save changes in their browser session.

Perhaps share some more details so we can give taylored advice.

Tony

[Arlen Beiler]

If your site is mostly static, then use individual static HTML files exported using the examples on TiddlyWiki.com. 

If it is mostly interactive, or has a lot of cross-reference links that would benefit from a story river, then use the single file approach and insert pictures as relative links (using '[img[files/pic.png]]'). Unless you have a huge site, this should be a workable option. The best way is to put everything in one folder and name your wiki "index.html" then put all supporting files in a "files" folder beside it and use relative links. 

The third option is just to put everything in one file, but that is only useful for places where you can't use relative links easily. 

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 post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3cf2a366-d384-4a67-866a-eee642994576%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kalcifer Kandari]

Okay, I suppose I'll see if the text outgrows the single '.html' file approach with the splash screen, while keeping media relatively linked.

I would like to know a bit about TiddlyWiki versus NoteSelf. Comparing them:

• How do I host without the public being able to change what is being hosted on the server? I don't mind if they can change their local version.
  
• What is the workflow for making changes to the hosted file? For example, is this done directly as in NoteSelf's CouchDB sync, or is a local copy changed and uploaded using SSH?
• Are there any other differences I should know about?

[TonyM]

How do I host without the public being able to change what is being hosted on the server?

Jusy put the html in a hosted location, name it index.html to load by default at the address and or foldername it is in.

What is the workflow for making changes to the hosted file? For example, is this done directly as in NoteSelf's CouchDB sync, or is a local copy changed and uploaded using SSH?

I think both are possible, but with no couchdb you can only use the second, and the local pouchdb in the browser will be used. Saving the lical copy involves a save over the existing file. Make sure it captures your changes in another browser.

Are there any other differences I should know about?

Tiddlers are version controled
You may need to use the plugin version to get the latest tw version.
I have not put it in production yet, so cant be sure thats everything.

Regards
Tony

[Kalcifer Kandari]

Nice, I got the basic '.html' version running. NoteSelf looks interesting just for the tiddler revisions, but I don't know how to set it up so the public can access it where only I can edit it, or how to back it up.

Anyway, thanks for the help!

[TonyM]

You already have the anser, yourself, confirmed by me for noteslf.

a local copy changed, [saved over] and uploaded using SSH?

By tge way if you are using an apache php host there is another way.

Regards
Tony

[Kalcifer Kandari]

So with NoteSelf, you put the '.html' file in the public folder, then install CouchDB on the same host? If that is true, and I haven't tried, wouldn't the public be able to edit the database then through the '.html' file because they are linked?

My host is nearlyfreespeech.net, they do Apache, but support custom servers like node.js as well. What is this other way?

[TonyM]

Kal,

With noteself if you do not set up a counchDB, it uses pouchDB (in the browser session automatically, no setup). Just copy the notself html to the shared location, and people can save there, their own edits (in the browser session) and the html sits unmodified. You can open your own copy in your browser, but to save changes must overwrite the html file - then copy it up to your host. I will retest this workflow myself.

The simplest way is to simply place a single file wiki online, and provide no way for people to save without saving to their own disk. You on the other hand could use a webDrive to access and save it, or transfer it when ready "publish" updates".

TiddlyWIki offers so many ways to host it if you have a host such as yours (and my own)  I would not do it justice here, so I will give you a few pointers but you may need to do more research.

 

• TW-Reciever is a PHP  saver Discussion Github https://github.com/sendwheel/tw-receiver
  
• If you want multiple users at a time look at NodeJS, Bob 
• If you want multiple access levels on Node look at the TiddlyWiki 5.1.17 - 5.1.19 release notes for new user/auth features
  

There is material around to help you make these decisions, I suggest you document your needs then start some research if none of the above seem right for you.

http://setup.tiddlyspot.com/ is a work in progress resource and needs more data but it may get you started.

Regards

Tony

[Kalcifer Kandari]

I see, I was misinterpreting something I read elsewhere.

Thanks for the tips, much easier to make an educated decision when the options are listed in one place for comparison. What I have now is working nicely so far.

Thanks again!