nimbus-eth2/scripts/package_src/nimbus_beacon_node/after_install

#!/bin/bash

set -e

DISTRO=$(lsb_release -si)
if ! id -u nimbus > /dev/null 2>&1; then
  case $DISTRO in
    Ubuntu|Debian)
      # Debian uses `adduser` to create user...
      adduser --system --no-create-home --group nimbus
      ;;
    *)
      # ... while `useradd` is more standard
      useradd --system --no-create-home --user-group nimbus
      ;;
  esac
fi

mkdir -p /var/lib/nimbus
chown nimbus:nimbus /var/lib/nimbus

systemctl daemon-reload
RPM/DEB for systemd-based systems (#3034) * RPM/DEB for systemd-based systems Similar to https://github.com/status-im/nimbus-eth2/pull/2691, this PR introduces packaging for nimbus beacon node. Instead of relying on interactive prompts, a default configuration is included that connects to mainnet and expects there to be an execution client running with websockets enabled on the same host, on the standard websocket port. Should the user need to configure their nimbus after installation (for example with a different web3 url), the "standard" way of doing so via `systemctl` edit is recommended. 2021-12-07 14:23:57 +01:00			`#!/bin/bash`

			`set -e`

			`DISTRO=$(lsb_release -si)`
			`if ! id -u nimbus > /dev/null 2>&1; then`
			`case $DISTRO in`
			`Ubuntu\|Debian)`
packaging updates (#3974) * packaging updates * one package per binary (nimbus_beacon_node, nimbus_validator_client) * use `-` in package name (`_` is separating the version) * don't include (un)installation scripts in package * default metrics port 8108 for vc * fix several upgrade/install errors in scripts * add JWT option to service files * don't attempt to remove user on purge 2022-08-17 12:26:31 +02:00			# Debian uses `adduser` to create user...
RPM/DEB for systemd-based systems (#3034) * RPM/DEB for systemd-based systems Similar to https://github.com/status-im/nimbus-eth2/pull/2691, this PR introduces packaging for nimbus beacon node. Instead of relying on interactive prompts, a default configuration is included that connects to mainnet and expects there to be an execution client running with websockets enabled on the same host, on the standard websocket port. Should the user need to configure their nimbus after installation (for example with a different web3 url), the "standard" way of doing so via `systemctl` edit is recommended. 2021-12-07 14:23:57 +01:00			`adduser --system --no-create-home --group nimbus`
			`;;`
packaging updates (#3974) * packaging updates * one package per binary (nimbus_beacon_node, nimbus_validator_client) * use `-` in package name (`_` is separating the version) * don't include (un)installation scripts in package * default metrics port 8108 for vc * fix several upgrade/install errors in scripts * add JWT option to service files * don't attempt to remove user on purge 2022-08-17 12:26:31 +02:00			`*)`
			# ... while `useradd` is more standard
			`useradd --system --no-create-home --user-group nimbus`
RPM/DEB for systemd-based systems (#3034) * RPM/DEB for systemd-based systems Similar to https://github.com/status-im/nimbus-eth2/pull/2691, this PR introduces packaging for nimbus beacon node. Instead of relying on interactive prompts, a default configuration is included that connects to mainnet and expects there to be an execution client running with websockets enabled on the same host, on the standard websocket port. Should the user need to configure their nimbus after installation (for example with a different web3 url), the "standard" way of doing so via `systemctl` edit is recommended. 2021-12-07 14:23:57 +01:00			`;;`
			`esac`
			`fi`

			`mkdir -p /var/lib/nimbus`
			`chown nimbus:nimbus /var/lib/nimbus`

			`systemctl daemon-reload`