Start ChromeDriver as a daemon on Forge?

I need to have ChromeDriver running all the time on my server.

If i ssh to my server and start ChromeDriver manually:

ssh forge@___.___.___.___
cd /usr/bin
./chromedriver

I get: Starting ChromeDriver 102.0.5005.61 (0e59bcc00cc4985ce39ad31c150065f159d95ad3-refs/branch-heads/5005@{#819}) on port 9515

Only local connections are allowed.

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.

ChromeDriver was started successfully.

and if i open another shell to check that it was started:

ssh forge@___.___.___.___
ps -a

I get: PID TTY TIME CMD

52856 pts/1 00:00:00 chromedriver

52875 pts/0 00:00:00 ps

So ChromeDriver does get started, it works, i'm happy.

BUT now, this is actually really inconvenient to start ChromeDriver manually from a terminal, because i need it running all the time. What happens if my terminal is terminated for any reason?

Which is why i looked into daemons. So if i start ChromeDriver as a daemon in Forge: /usr/bin/chromedriver the log file /home/forge/.forge/daemon-______.log does say that ChromeDriver was started: Starting ChromeDriver 102.0.5005.61 (0e59bcc00cc4985ce39ad31c150065f159d95ad3-refs/branch-heads/5005@{#819}) on port 9515

Only local connections are allowed.

Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.

ChromeDriver was started successfully.

but if i check what processes are running on my server, now ChromeDriver does NOT show.

ssh forge@___.___.___.___
ps -a

gives: PID TTY TIME CMD

53130 pts/0 00:00:00 ps

Is it normal because daemons work differently? Is my ChromeDriver actually started?

Is there a better way to start ChromeDriver if i want to keep it running all the time or are daemons the best way?

I looked into recipes as well, but it feels weird to have a recipe never stop... Thanks.