Announcing the release of deepstream.io 2.4, which now supports running deepstream as a daemon and registering itself as a service via init.d or systemd.
Registering as a linux service
If you are running any linux distro chances are you support either init.d (AWS/CentOS) or systemd (Ubuntu/debian). Using the new service installer means downloading deepstream and getting it to run as a service and auto-restart to avoid downtime is as easy as
# When using YUM sudo wget https://bintray.com/deepstreamio/rpm/rpm -O /etc/yum.repos.d/bintray-deepstreamio-rpm.repo sudo yum install -y deepstream.io # Install as a init.d service sudo deepstream service add # Start the service sudo deepstream service start
Running a daemon
For those running servers on windows or mac, although we currently don't support as a native service on those platforms you can still run the daemon to monitor and auto-restart deepstream if necessary, while still supporting al the normal start options
deepstream daemon --help Usage: daemon [options] start a daemon for deepstream server Options: -h, --help output usage information -c, --config [file] configuration file, parent directory will be used as prefix for other config files -l, --lib-dir [directory] path where to lookup for plugins like connectors and logger --server-name <name> Each server within a cluster needs a unique name --host <host> host for the HTTP/websocket server --port <port> port for the HTTP/websocket server --disable-auth Force deepstream to use "none" auth type --disable-permissions Force deepstream to use "none" permissions --log-level <level> Log messages with this level and above
Installing via brew cask
brew cask install deepstream
And install plugins from anywhere
deepstream install msg redis => deepstream.io-msg-redis v1.0.4 was installed to /usr/local/lib/deepstream
So let brew deal with installing and upgrading, so that you don't have to!