These steps work for me. If they work for you, maybe it can help you track
down your issue:

1. mkdir simple-tw-npm-test
2. cd simple-tw-npm-test
# Ignore warnings here about missing package.json
3. npm install tiddlywiki
4. $(npm bin)/tiddlywiki wiki --init server
5. $(npm bin)/tiddlywiki wiki --listen
6. visit http://127.0.0.1:8080 in your browser


The tiddlers will be stored in the relative folder named 'wiki'

BTW, '$(npm bin)' syntax in #4 and #5 is for bash. If you aren't using
Linux or Mac, then likely you aren't using bash. If that's the case, then
run the 'npm bin' command by itself and replace the '$(npm bin)' above with
the output you see. Also if you are on windows I guess you would need to
replace the forward slash with back slash.

Now after typing this, I just realized it should be documented already and
I find it is: https://tiddlywiki.com/#Installing%20TiddlyWiki%20on%20Node.js.
Are these the instructions you are already following?

Brian

On Mon, Feb 4, 2019 at 2:01 PM stefano franchi <[email protected]>
wrote:

>
>
> I'm encountering more troubles getting a demo wiki to work after setting
> up the node/tiddlywiki as recommended. Two issues:
>
> 1. I cloned the TW5 repo from github into a local dir under my home dir
> and modified the tw5.com tiddlywiki.info file as per on the devs site. I
> also have a global version of the tiddlywiki source code installed in
> /usr/lib. I cannot seem to find a way to convince the tiddlywiki executable
> to look into the local version of the "editions" folder. It always uses the
> global file in /ur/lib. If I try to pass the full path to the local version
> of tw5.com to the tiddlywiki --init command, it always complains that the
> file cannot be found.
>
> 2. If I do try to install a server version based on the global tw.com
> templates, I end up being unable to start the server, because tiddlywiki
> stops booting process complaining it cannot find the ca-ES.tid file.
> Unsurprisingly so, since it looks for it in the wrong place, using a
> relative path that leads it astray. Using the path-prefix options does not
> seem to have any effect.
>
> This is very frustrating.  I must be approaching what I I thought would be
> a relatively  simple task the wrong way, . Either that or I am really dumb.
>
> Any suggestions?
>
>
> Cheers,
>
> Stefano
> --
> __________________________________________________
> Stefano Franchi
>
> [email protected] <[email protected]>
> http://stefano.cleinias.org
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" 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/tiddlywikidev.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywikidev/CAJODLwaGVU2pFTRVy553Xg45Y-c3pNQvqHp2n2L%2BgC%3Dogk9y5g%40mail.gmail.com
> <https://groups.google.com/d/msgid/tiddlywikidev/CAJODLwaGVU2pFTRVy553Xg45Y-c3pNQvqHp2n2L%2BgC%3Dogk9y5g%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAO5X8CzxNGPDVgY-SgFnUU0XbyfdAZo8U9EF6HYeJHjxBPtXeA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to