third-party-mirrors/EDDN
1
0
Fork 0
mirror of https://github.com/EDCD/EDDN.git synced 2025-04-26 13:12:13 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity
EDDN/contrib/systemd
History
Athanasius 086493b5bf Make it possible to split dev and live installs 
* Have 'dev' and 'live' components to many paths and file names.
* Have separate dev/live systemd start script configs.
* Have the systemd start script take a dev/live second argument.
* Try to ensure permissions on 'web' files by explicitly setting umask.
2021-07-01 16:52:25 +00:00
..
eddn_dev_config
Make it possible to split dev and live installs
2021-07-01 16:52:25 +00:00
eddn_live_config
Make it possible to split dev and live installs
2021-07-01 16:52:25 +00:00
eddn.target
Add example systemd unit files, and supporting files.
2021-06-14 12:27:21 +01:00
eddn@.service
systemd: Correct AssertPathExists to python venv
2021-06-14 17:32:13 +01:00
README.md
Add example systemd unit files, and supporting files.
2021-06-14 12:27:21 +01:00
start-eddn-service
Make it possible to split dev and live installs
2021-07-01 16:52:25 +00:00

README.md

systemd unit files for running EDDN services

eddn.target

This is a systemd target specifying that each of the services be run. Place it in /etc/systemd/system.

eddn@.service

This is a systemd template service file, negating the need for a separate file per service.

Place it in /etc/systemd/system. Edit it for:

  1. AssetPathExists - The path to where python setup.py install --user installed the files: eddn-gateway, eddn-monitor, eddn-relay.
  2. ExecStart - The path to where the wrapper scripts (see below) are installed. Probably the same path.
  3. The User and Group you need the services to run as.

Wrapper scripts

Each service is started by a wrapper script:

  • start-eddn-gateway
  • start-eddn-monitor
  • start-eddn-relay

Each of these utilises the file eddn_config for some basic configuration:

  • The config override file to be used.
  • The directory to redirect all output to.

Each script will start its service with output redirected to an appropriate file in the configured log directory, e.g.:

./eddn-gateway --config "${CONFIG_OVERRIDE}" >> "${LOG_DIR}/eddn-gateway.log" 2>&1