#!/bin/bash SECRET_KEY_BASE="$SERVICE_DATASTORE"/secret-key ## Erlang release cookie. The image ships one in ``/app/releases/COOKIE`` ## that is generated when the image is built, so it is the same for every ## installation of that image: replace it by one of our own. RELEASE_COOKIE_FILE="$SERVICE_DATASTORE"/release-cookie SHARE_DIR="$SERVICE_DATASTORE"/var/lib/plausible mkdir -p $SHARE_DIR uid=$(docker_get_uid "$SERVICE_NAME" "plausible") if ! [ -f "$SECRET_KEY_BASE" ]; then info "Generating secret key" mkdir -p "${SECRET_KEY_BASE%/*}" umask 077 openssl rand -base64 64 > "$SECRET_KEY_BASE" else info "Using existing secret key" fi if ! [ -f "$RELEASE_COOKIE_FILE" ]; then info "Generating Erlang release cookie" mkdir -p "${RELEASE_COOKIE_FILE%/*}" (umask 077; openssl rand -hex 32 > "$RELEASE_COOKIE_FILE") fi secret_key_base=$(cat "$SECRET_KEY_BASE") release_cookie=$(cat "$RELEASE_COOKIE_FILE") ## ``RELEASE_DISTRIBUTION: none``: Plausible Community Edition runs a ## single node and never needs Erlang distribution (the ``db createdb`` and ## ``db migrate`` commands use ``eval``), so the node opens no ``epmd`` nor ## distribution port that anything else could connect to. init-config-add " $SERVICE_NAME: environment: SECRET_KEY_BASE: \"$secret_key_base\" RELEASE_COOKIE: \"$release_cookie\" RELEASE_DISTRIBUTION: \"none\" " chown -v "$uid" "$SHARE_DIR"