README could use clearer example on how to get teleIRC running as a background process about teleirc HOT 11 OPEN

I'm not sure how I got it working last night, using teleirc & isn't working today, and neither is prefixing that with nohup. Will go poke around some more until it works.

from teleirc.

The command nohup teleirc 2> /dev/null & seemed to do the trick! I'm not sure if the nohup is strictly necessary or not, but sending the output to /dev/null seems to make the bot stay connected when someone sends a message and the terminal session is closed.

from teleirc.

Why not just run it within tmux or screen?

from teleirc.

Why not just run it within tmux or screen?

I think I figured out what was causing my issues. I did use tmux the first time I solved this issue. However, I had forgotten that I detached with d instead of killed the pane with x, so it didn't work the next time I tried with tmux. I'm not familiar with screen, but I'll look into it.

Putting a note to send the output to /dev/null or to use tmux or screen (and detach from, not kill, the pane) in the optional part of the quickstart section is my preferred solution. Does that sound reasonable?

from teleirc.

I recommend running node applications through pm2 personally

from teleirc.

I've been running it as a systemd unit myself. We should investigate a solution that works for everyone and document that in the README. What do you people think of foreverjs for example, could we recommend usage of this one officially?

from teleirc.

I always had issues with nohup
personally I just background it and send it to init
node teleirc.js >/dev/null & disown
then I usually make a pidfile so I can SIGTERM it later,
echo $! >teleirc.pid

from teleirc.

http://devo.ps/blog/goodbye-node-forever-hello-pm2/ good comparison here

from teleirc.

Thanks, will consider this one

from teleirc.

I am not sure if I understand the issue correctly.

Anyway, I would highly recommend GNU screen or TMUX.

If some one doesn't want logs, they can run teleirc & and that should keep it going.

from teleirc.

At this point the documentation on how to start the bot with pm2 is wrong (there is no teleirc.js) and there is no indication how to do it right.

from teleirc.