2021-05-19 07:49:23 +02:00
# cc-docker
2021-05-19 07:53:28 +02:00
2021-06-14 11:23:04 +02:00
This is a setup for `docker compose` to try out a complete ClusterCockpit Application Stack including all external components. This docker setup is intended for demo purposes, but can be easily configured to be used as a development environement for ClusterCockpit.
2021-05-19 14:56:25 +02:00
2021-06-14 11:09:57 +02:00
It creates containers for:
2021-05-19 14:56:25 +02:00
* mysql
2021-06-15 16:45:15 +02:00
* php-fpm
2021-05-19 14:56:25 +02:00
* nginx
2021-06-22 13:37:35 +02:00
* influxdb (only in dev mode)
2021-06-15 16:45:15 +02:00
* phpmyadmin (only in dev mode)
2021-05-19 14:56:25 +02:00
2021-06-14 11:09:57 +02:00
Ports and Passwords are configured in `.env` .
2021-05-19 07:53:28 +02:00
2021-05-19 14:56:25 +02:00
TODOS (There are probably a lot more!):
2021-05-21 08:54:24 +02:00
* Some of the Volume directories need to be created first.
2021-05-19 14:56:25 +02:00
* ClusterCockpit is at the moment still using the influxDB V1 API, the InfluxDB container is already V2
2021-06-10 12:08:22 +02:00
* For a complete demo database setup, InfluxDB data fixtures are missing (MySQL demo database is available)
2021-06-09 09:53:35 +02:00
2021-06-11 13:44:51 +02:00
## Known Issues
2021-06-09 09:53:35 +02:00
2021-06-10 13:21:59 +02:00
* `docker-compose` installed on Ubuntu (18.04, 20.04) via `apt-get` can not correctly parse `docker-compose.yml` due to version differences. Install latest version of `docker-compose` from https://docs.docker.com/compose/install/ instead.
2021-06-10 12:08:22 +02:00
* You need to ensure that no other web server is running on port 80 (e.g. Apache2). If port 80 is already in use, edit NGINX_PORT environment variable in `.env` .
* Existing VPN connections sometimes cause problems with docker. If `docker-compose` does not start up correctly, try disabling any active VPN connection. Refer to https://stackoverflow.com/questions/45692255/how-make-openvpn-work-with-docker for further information.
2021-06-11 13:44:51 +02:00
## Using for DEMO purpose
### Info
* Demo starts in production environment.
* Uses prepared fixture data for databases (Changes will not be preserved).
2021-06-15 16:45:15 +02:00
* ClusterCockpit is initialized from scratch on every container start (Changes will not be preserved).
2021-06-11 13:44:51 +02:00
### Setup
2021-06-15 16:45:15 +02:00
The fixture data needs to be prepared once before first start of containers:
2021-06-11 13:44:51 +02:00
* `$ cd data`
* `$ ./init.sh`
2021-06-09 09:53:35 +02:00
After that from the root of the repository you can start up the containers with:
* `docker-compose up`
* Wait... and wait a little longer
2021-06-15 16:45:15 +02:00
By default, you can access ClusterCockpit in your browser at http://localhost . If the `NGINX_PORT` environment variable was changed, use `http://localhost:$PORT` .
2021-06-10 12:08:22 +02:00
2021-06-09 09:53:35 +02:00
Credentials for admin user are:
* User: `admin`
* Password: `AdminDev`
2021-06-10 12:08:22 +02:00
You can shutdown the containers by pressing `CTRL-C` .
2021-06-09 09:55:54 +02:00
2021-06-11 13:44:51 +02:00
To reuse an existing Symfony tree at `./data/symfony` you may change the environment variable `APP_CLUSTERCOCKPIT_INIT` in `.env` from `true` to `false` .
## Using for DEVELOP purpose
### Info
2021-06-15 17:09:53 +02:00
* `APP_ENVIRONMENT` variable in `.env` used to switch `php-fpm` container to development environement.
2021-06-11 13:44:51 +02:00
* `APP_CLUSTERCOCKPIT_INIT` variable in `.env` used to prevent container from initializing a new ClusterCockpit instance on every start.
* In this case, an existing Symfony tree at `./data/symfony` is required.
2021-06-15 17:09:53 +02:00
* By default, this also uses prepared fixture data for databases. In order to use an existing database, changes in `.env` and `docker-compose.yml` are required (see below).
2021-06-11 13:44:51 +02:00
### Setup
2021-06-22 13:36:08 +02:00
This description assumes you will let the docker setup initialize the symfony tree and data fixtures for you.
2021-06-11 13:44:51 +02:00
If not using an existing database, the fixture data needs to be prepared before the first start of the containers:
* `$ cd data`
2021-06-22 13:36:08 +02:00
* `$ ./init.sh dev`
2021-06-11 13:44:51 +02:00
In `.env` , change the following variables under `APP`
* `APP_ENVIRONMENT` to `dev`
2021-06-22 13:36:08 +02:00
After that from the root of the repository you can start up the containers with (use -d switch to startup in detached mode):
2021-06-15 17:09:53 +02:00
* `docker-compose -f docker-compose.yml -f docker-compose-dev.yml up`
2021-06-11 13:44:51 +02:00
* Wait... and wait a little longer
2021-06-15 17:45:18 +02:00
After the initial setup you have to:
* Comment or delete the line `- ${DATADIR}/sql:/docker-entrypoint-initdb.d` for `cc-db` to disable initialisation of the MySQL database.
* Set `APP_CLUSTERCOCKPIT_INIT` to `false` in the .env file
2021-06-22 13:36:08 +02:00
On subsequent start of the containers you will then reuse the persisted volume data located in the `./data` directory.
2021-06-15 17:45:18 +02:00
2021-06-15 17:12:28 +02:00
By default, you can access ClusterCockpit in your browser at `http://localhost` .
If `NGINX_PORT` environment variable was changed, `use http://localhost:$PORT` .
The InfluxDB Web interface can be accessed at `http://localhost:8086` using the credentials set in `.env` .
2021-06-15 17:36:17 +02:00
PHPMyAdmin can be reached at `http://localhost:8080` .
2021-06-11 13:44:51 +02:00
If default database fixture were used, the credentials for admin user are:
* User: `admin`
* Password: `AdminDev`
2021-06-22 13:36:08 +02:00
You can shutdown the containers by pressing `CTRL-C` if not started in detached mode.