-
* we're going for a small single-machine setup here * we don't include logstash/fluentd in the setup; this is off-loaded to other projects sending their logs to OS deployments * configure the security plugin to use self-generated certificates, and create a bunch of customized internal users * note: apparently, securityadmin's '-rev' flag doesn't do anything for internal_users * instead, we need to go the good old 'sed' route to update the internal users
* we're going for a small single-machine setup here * we don't include logstash/fluentd in the setup; this is off-loaded to other projects sending their logs to OS deployments * configure the security plugin to use self-generated certificates, and create a bunch of customized internal users * note: apparently, securityadmin's '-rev' flag doesn't do anything for internal_users * instead, we need to go the good old 'sed' route to update the internal users
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
setup.sh 457 B
#!/bin/bash
#
# script for setting up and running the log server
set -euo pipefail
if [[ ! -d "ssl" || ! -f "docker-compose.yml" || ! -f "docker-compose.base.yml" ]]; then
echo >&2 "error: this script needs to be executed from the project directory!"
exit 1
fi
# generating the ssl key pairs
./scripts/generate-ssl.sh
# initialize the security configuration
docker compose run os-node-1 ./init-security.sh
# run the server
docker compose up -d