Hi James
Glad you've got things working.
Not sure why $HOME is needed, but it seems to be:
The reason is that you've omitted the wiki folder from the tiddlywiki
command line, causing it to default to the current folder. You could
rephrase the command as:
exec /home/james/local/bin/node
Supervisor may well be the way to go, I'll have a look into it.
Meanwhile...
I've just updated Tiddlywiki to 5.1.5 from one of the betas - it broke and
I couldn't get at it from the browser at all.
After much fiddling about I've realised that it's now serving from
127.0.0.1 in order to get it
Actually I see now that this was covered in a few other threads, probably
worth mentioning in regard to these scripts anyway.
On Monday, 15 December 2014 22:56:58 UTC, Wildscot wrote:
Supervisor may well be the way to go, I'll have a look into it.
Meanwhile...
I've just updated Tiddlywiki
Hi all,
Also found some useful hints from the install of ghost (which is also based
on node.js), for users of linux for example
http://docs.ghost.org/installation/deploy/
apt-get install supervisor
vi /etc/supervisor/conf.d/tiddlywiki.conf
```
[program:tiddlywiki]
command = node
Why not just use forever command?
https://www.digitalocean.com/community/articles/how-to-host-multiple-node-js-applications-on-a-single-vps-with-nginx-forever-and-crontab
Em quarta-feira, 15 de janeiro de 2014 15h58min37s UTC-2, Wildscot escreveu:
OK, after pulling my hair out for a couple of
The simple command:
forever start --spinSleepTime 1
/usr/local/lib/node_modules/tiddlywiki/tiddlywiki.js --server
works for me except that I can't figure out how to specify the directory
where that wiki lives on this command line. I assume this is why $HOME is
being redefined, but that
No, you have to forever start the bin:
forever start --spinSleepTime 1 ~/local/bin/tiddlywiki --server
--
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
And how to ser the name_server for DNS configuration?
Em quarta-feira, 15 de janeiro de 2014 15h58min37s UTC-2, Wildscot escreveu:
OK, after pulling my hair out for a couple of days I seem to have it
working.
I'll make it clear though this is all about cut paste and stubbornness
rather
OK, after pulling my hair out for a couple of days I seem to have it
working.
I'll make it clear though this is all about cut paste and stubbornness
rather than any real understanding, YMMV.
This is Tiddlywiki 5, Node.js install on a VPS running Ubuntu 12.04LTS,
launching at boot.
The same
OK, after pulling my hair out for a couple of days I seem to have it
working.
I'll make it clear though this is all about cut paste and stubbornness
rather than any real understanding, YMMV.
This is Tiddlywiki 5, Node.js install on a VPS running Ubuntu 12.04LTS,
launching at boot.
The same
Remember, depending on your environment you may need to change the
interface above.
I was testing on a local virtual machine with 'eth0' as the network
interface but the actual VPS doesnt.
$ ifconfig
will list your interfaces and edit accordingly.
On Wednesday, 15 January 2014 17:58:37 UTC,
Hi James
There's just been a similar question on GitHub:
https://github.com/Jermolene/TiddlyWiki5/issues/340
I don't personally have experience of these configurations, but would
welcome feedback so that I can add the necessary details to the
documentation.
Best wishes
Jeremy
On Sun, Jan
I've installed TW5 on a VPS with node.js. Thrilled with it, especially the
smooth functionality on mobile.
I've had a quick Google on starting a node.js server on boot, rather than
manually, and it seems upstart and forever are what I need to be getting my
head around?
I've not worked with
13 matches
Mail list logo
