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 for the TW and 8090 for the images. Just tested and this appears to actually work.
This means you can't use relative paths since you're going to have specify the IP:port for any image or file you're serving up. It's effectively the same as if you were referencing an image on a website somewhere. Good luck! Mark On Sunday, April 16, 2017 at 9:50:32 AM UTC-7, Jeff Vance wrote: > > 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 conflict running > them together and resolving the host. Starting the file server from the > root of the relative path, I could navigate to any file via localhost (when > TW is not running). But when TW server is running, the file paths don't > work anymore. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/888fcb4a-bca5-438f-97ba-73b43a13b0b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
