Run in detached mode 🔗

[jessicafarias]

In order to avoid to keep the terminal open and to have multiple paths listening.
I was wondering if you can implement a -d option to keep run and listening witouth having a terminal open (in detached mode or in the background from terminal).
And also a way to check all running process in smee such as docker does with -d and ps.
where: d=detach, ps=process status, rm [prcess_id] = remove/stop process

user@user:~$ smee -d
Forwarding https://smee.io/1PUc3ipJCAKIMTaR to http://127.0.0.1:3000/
Connected https://smee.io/1PUc3ipJCAKIMTaR
Detached

user@user:~$ smee ps
ID           URL                                     PATH      PORT
IDNAME       https://smee.io/1PUc3ipJCAKIMTaR         /        3000

OR:

user@user:~$ smee -d -u https://smee.io/new -P /custom_path/ -p 8080
Forwarding https://smee.io/new to http://127.0.0.1:8080/custom_path
Connected https://smee.io/new
Detached

user@user:~$ smee ps
ID             URL                                 PATH                PORT
NEWIDNAME      https://smee.io/new                 /custom_path        8080
IDNAME         https://smee.io/1PUc3ipJCAKIMTaR    /custom_path        8080

user@user:~$ smee rm NEWIDNAME
Stoping https://smee.io/new
Removed

I tried to use daemon on unix system to run it on background and I found it works for just one smee call. It doesn't work for more than 1 smee call because the smee stay alive when it displays "Connected".

[gr2m]

It doesn't work for more than 1 smee call because the smee stay alive when it displays "Connected".

I don't quite understand this sentence. Does the daemon crash after receiving the first event?

[jessicafarias]

I tried to create a new file that contains all smee calls that I need.
After following this tutorial and using this script:

#!/bin/bash
smee -u https://smee.io/custom_url/ -P /generic-webhook-trigger/invoke?token=one -p 8080
smee -u https://smee.io/custom_url/ -P /generic-webhook-trigger/invoke?token=two -p 8080
....
smee -u https://smee.io/tcustom_url/ -P /generic-webhook-trigger/invoke?token=eleven -p 8080

I notice it upload just the first line and ignores the others:

smee -u https://smee.io/custom_url/ -P /generic-webhook-trigger/invoke?token=one -p 8080

I also try to use \ command after each line and doesn't work.

I guessing this is because the first line keeps listening when it returns "Connected". It's my guessing because I notice a same behavior with & command in CLI.

user@user:~$ smee &
Forwarding https://smee.io/99hqrIEtrRkb0B8y to http://127.0.0.1:3000/
hConnected https://smee.io/99hqrIEtrRkb0B8y
------Ctrl+C----- to close smee on terminal and keep running on the background

I need to use Ctrl+C to manually exit to run in background otherwise it stay listening in the console.

[kadler]

Sounds like you have multiple smee listeners. You could use a tool like nohup to run each in the background in the same shell script (using redirects to save output to different files). Of course, this approach becomes more complicated because now you have to do the child handling in the shell script and if one dies it's not as easy to deal with.

Alternatively, it would be easier to put each listner in to a separate systemd unit files (using the tutorial you linked) and tie them all together using systemd, eg. a systemd target.

[wolfy1339]

Smee is not really intended to be run in the background. It is meant to be used for active development.