TiddlyWiki behind Apache as /zwiki/

513 views
Skip to first unread message

Eric Stephens

unread,
Mar 6, 2017, 8:38:50 AM3/6/17
to TiddlyWiki
I am trying to run the server on an existing Node.js box we have other applications running on.
Can some help me with the Apache magic to get the ajax calls working?
Or it may be the pathprefix does not work as I hoped.  http://tiddlywiki.com/static/ServerCommand.html

Here's my start command:

tiddlywiki mynewwiki --server 8081 $:/core/save/all text/plain text/html "" "" 127.0.0.1 /zwiki 

Here's the httpd.conf:

ProxyPassReverse /zwiki/ http://localhost:8081/zwiki/

Here are the errors:



Xavier Cazin

unread,
Mar 6, 2017, 10:21:44 AM3/6/17
to tiddl...@googlegroups.com
Hi Eric,

By any chance, did you load the mod_proxy_http module in addition to mod_proxy? This is mandatory and I've been caught several times by this one.

Also, I systematically set:

<Proxy *>
    Order Deny,Allow
    Allow from all
</Proxy>

Best,
X.

-- Xavier Cazin

--
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+unsubscribe@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/22a48864-dd27-4491-b605-7bb719c95d9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Lost Admin

unread,
Mar 7, 2017, 12:30:51 PM3/7/17
to TiddlyWiki
I'm curious. What is the benefit to running tiddlywiki on node.js on your server vs serving it up from Apache and using something like store.php to save changes?

Xavier Cazin

unread,
Mar 9, 2017, 1:04:20 PM3/9/17
to tiddl...@googlegroups.com
Hi Lost Admin,

Probably not much difference from the user point of view, unless you plan to work on a big wiki. From my perspective, the two main benefits of using the Node.js version are:
  1. Resources saving: when your wiki grows, and you add PDF files, pictures, or multiple plugins, the lazy loading mecanism helps you keep your browser usable. Also, depending of your backup policy, you may end up with a new version of your main wiki laying around on your server each time you add or modify content.
  2. Flexibility: having one file per tiddler makes it easier to communicate with the outside world. Good for backups but also for producing and organising tiddlers from external content.

The one thing that I miss from using a single HTML file is the ability to cypher the whole wiki with a single passphrase.

Best, 

Xavier. 


-- Xavier Cazin

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
Reply all
Reply to author
Forward
0 new messages