Please install docker and docker-compose.
Then, we’ll fetch three files.
mkdir centralized
cd $_
for i in docker-compose.yml base.yml configuration.env.doc; do
curl -O https://raw.githubusercontent.com/sisu-centralized/centralized/master/$i
done
mv configuration.env.doc configuration.env
Let’s edit configuration.env
# Postgres DB config
POSTGRES_USER='centralized' # Do not change.
POSTGRES_PASSWORD='' <----- Set this to any non empty value.
POSTGRES_DB='centralized' # Do not change.
CONNECTOR_TYPE=github <----- Or bitbucket.
CONNECTOR_USERNAME= <----- Username of a github user part of your github organization or bitbucket user part of your team. The user doesn't need access to any repository.
CONNECTOR_PASSWORD= <----- Password of the github/bitbucket user or githubtoken for 2FA.
ORG_NAME= <----- Name of your organization. In case of github, this must be the github organization.
ORG_CONTACT= <----- Name of the person in charge of deploying centralized.
ORG_EMAIL= <----- Email of the person in charge of deploying centralized.
FIRSTADMIN=centralized_admin
# SMTP SSL supported only for now, PRs welcome!
# https://docs.python.org/3/library/smtplib.html
SMTP_SERVER= <----- All those are helpful only in case you plan to have multiple admin users.
SMTP_PORT= <----- They are mainly used in admin password resets, etc...
SMTP_PASSWORD= <----- You can try and use centralized without those at least at the begining.
That’s it! Centralized is configured.
Let’s start it!
docker-compose up -d
Now that the service is running, it also creates a directory: /tmp/centralized.
This directory contains the following files:
admin_account.text <---- Here are your first admin login and password, no necessary for now, we don't have yet the web interface.
centralized_admin.json <---- Configuration file for the admin tool, includes login, password, CA, url... well, everything.
config.ini <---- Configuration file to copy on managed systems (see below), contains URL, organization ID and CA.