#
eramba
Eramba is a "community driven GRC solution that doesn't break the bank."
#
Install (Docker)
#
Download the stuff
I went the Docker install route as it was pretty easy to follow:
# Clone repo
git clone https://github.com/eramba/docker ~/eramba
cd ~/eramba
#
Edit the .env file
nano .env
DB_HOST=mysql
DB_DATABASE=docker
DB_USERNAME=docker
# change the DB_PASSWORD to something unique:
DB_PASSWORD=CHANGE ME
CACHE_URL=Redis://?server=redis&port=6379&password=&timeout=3
# change the MYSQL_ROOT_PASSWORD to something unique:
MYSQL_ROOT_PASSWORD=CHANGE ME
USE_PROXY=0
PROXY_HOST=
PROXY_PORT=
USE_PROXY_AUTH=0
PROXY_AUTH_USER=
PROXY_AUTH_PASS=
# The PUBLIC_ADDRESS and port becomes important - especially if you're going to give this thing a public IP/FQDN:
PUBLIC_ADDRESS=https://yourdomain-or-subdomain.com:SOMEPORT
DOCKER_DEPLOYMENT=1
LDAPTLS_REQCERT=never
In the config file above, the default port is 8443 but that's the same port my external firewall listens on. So where it says https://yourdomain-or-subdomain.com:SOMEPORT I did https://mydomain.com:8000. Then I also did the next step:
#
Edit the docker-compose.simple-install.yml
nano docker-compose.simple-install.yml
Look for the section that has an external to internal port mapping:
eramba:
container_name: eramba
image: ghcr.io/eramba/eramba:latest
restart: always
ports:
- 8000:443
(The 8000 is 8443 by default, so I changed this setting so that my eramba instance can be available on https://mydomain.com:8000)
#
Fire up the eramba instance
docker compose -f docker-compose.simple-install.yml up -d
#
Shut down eramba instance
docker compose -f docker-compose.simple-install.yml down
#
Troubleshooting
#
Review container logs
If something is jacked with your docker run, the logs might help you figure out what's up:
sudo docker logs -f eramba