Yes, that's the one I tried also.
It appears that you can't run both services on local host. But you can
specify your host IP number for each (which is what you want if you want
other devices on the network to see your tiddlywiki). But you need to
specify a different port number. So maybe 8080
Hi Mark: this is interesting. Exploring your idea of using another
node.js application to serve files, I found this:
https://github.com/indexzero/http-server
I tried it on its own and it works very well, but not sure how to make it
play nicely with TiddlyWiki. Maybe there is some sort of
Ok, thanks for the clarification and tips! I was not using relative
external links before (I wasn't aware that was possible). I'm definitely
switching to that way of linking now. Especially since most of the stuff I
link to are in a dropbox folder and I'm running out of storage (for the
To clarify, TiddlyWiki running on node.js doesn't serve up images or other
files. There are other applications running on node.js that do serve up
images and that is one of the easiest ways to add a server to your set up
if you want to go that route.
Thanks,
Mark
On Saturday, April 15, 2017
Just a few suggestions as I don't have the time right now to do a deeper
look at the problem:
Node.JS can serve up images, video, or anything else you might want.
Whether TiddlyWiki itself though is coded for that, I'm not sure. Normally
one simply assigns a route using Express.JS middleware
If you have any external images, they will also not show up.
node.js only serves up tiddlers, nothing else. Apparently modern browsers
won't let you link to a local file or image from page served up by a server
(which is how it views files from node.js). So, if you needed those images
or
6 matches
Mail list logo
