Best Practice Running Laravel Echo Server as Background Service about laravel-echo-server

[andkom]

example pm2 configuration:

echo.json:

{
  "name": "echo",
  "script": "laravel-echo-server",
  "args": "start"
}

command:

pm2 start echo.json

[jonnywilliamson]

Here's a copy of the supervisor config file I have for my echo server for a rough guideline (on a vagrant machine)

[program:echo-server]
directory=/home/vagrant/path/to/your/project
command=/usr/bin/laravel-echo-server start
autostart=true
autorestart=true
user=vagrant
redirect_stderr=true
stdout_logfile=/home/vagrant/path/to/your/project/storage/logs/echoserver.log

[KrzysztofHajdamowicz]

Systemd unit:

[Unit]
Description=Start a laravel-echo-server
After=network.target

[Service]
User=USER
Group=GROUP
WorkingDirectory=/var/lib/html/project
ExecStart=/usr/bin/laravel-echo-server start

Restart=on-failure

[Install]
WantedBy=multi-user.target

[wa05]

I cant set PM2 (2.6.1) on Windows 7 with Node v8.1.4

PM2 Log:

C:\USERS\WALTER\APPDATA\ROAMING\NPM\LARAVEL-ECHO-SERVER.CMD:1
(function (exports, require, module, __filename, __dirname) { @if EXIST "%~dp0\node.exe" (
^
SyntaxError: Invalid or unexpected token
at createScript (vm.js:74:10)
at Object.runInThisContext (vm.js:116:10)
at Module._compile (module.js:533:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Object. (C:\Users\Walter\AppData\Roaming\npm\node_modules\pm2\lib\ProcessContainerFork.js:70:21)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)

I'll try to run laravel-echo-server from a .bat and start the .bat with the Windows task scheduler or try to make work Supervisord on Windows creating a service with cygwin and python.. :/

[barryvdh]

You can also just restart with supervisor. Don't know if there is a 'graceful' restart, but with the latest echo, the clients should just reconnect when the server is back.

[feenx]

I'm running it with supervisor right now. Working perfectly for me, on my production server I've done the same except I had to use an absolute path to node in order to get the global installation of this package to fire up properly but it works great now.

[bendo01]

@pfeiferchristopher Thank You, I Will Try It With Supervisor

[jonnywilliamson]

@andkom Just to clarify though, using PM2 doesn't help with regard restarting the process if it exits? You'd still need supervisor/upstart etc?

[trip-somers]

Is there a way to kill/restart the Laravel Echo Server when/if a new configuration goes live? This would be something akin to how Laravel allows you to restart your queue workers: php artisan queue:restart

[trip-somers]

Does no one ever need to restart their Echo server?

[andkom]

@jonnywilliamson

pm2 restart echo

will restart echo process

[trip-somers]

Thanks, @barryvdh. I finally had time to look into that. I probably should have looked there first.

[ThunderBirdsX3]

@andkom How to call with config file laravel-echo-server.json

[catalinux]

That json config file it will be loaded by default. You need to run the server in the directory where the config file is placed

[jartaud]

Same as @wa05 comment

Node: v8.9.1
Npm: 5.5.1
Win10

[wa05]

@jartaud tell me if you can run the daemon with this https://github.com/coreybutler/node-windows

[anddyyao]

Same as @wa05
why

[wa05]

Finally Im running it with windows task manager..

[peters305]

You can also just restart with supervisor. Don't know if there is a 'graceful' restart, but with the latest echo, the clients should just reconnect when the server is back.

Hey Barry if you don't mind its little bit late but i was asking i want to start laravel-echo-server but i have dist folder after running npm build which includes index.html file how can start this