ClusterCockpit/cc-docker
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-docker.git synced 2024-12-26 07:19:04 +01:00
Code Issues Packages Projects Releases Wiki Activity
A configurable docker compose setup for development and testing of ClusterCockpit
10 Commits 3 Branches 1 Tag 894 KiB
Shell 53.3%
Perl 33.5%
Dockerfile 12.4%
Makefile 0.8%
d29e9aceec
Go to file
Jan Eitzinger d29e9aceec Fix errors. Add Symfony entrypoint.
2021-05-21 08:08:04 +02:00
nginx Fix errors. Add Symfony entrypoint. 2021-05-21 08:08:04 +02:00
php-fpm Fix errors. Add Symfony entrypoint. 2021-05-21 08:08:04 +02:00
.env Add configuration file 2021-05-19 14:57:19 +02:00
docker-compose.yml Fix errors. Add Symfony entrypoint. 2021-05-21 08:08:04 +02:00
LICENSE Initial commit 2021-05-19 07:49:23 +02:00
README.md Update readme 2021-05-19 14:56:25 +02:00

README.md

cc-docker

WARNING: This does not yet work!

This is a setup for docker compose to deploy a complete ClusterCockpit Application Stack including all external components.

At the end it will create containers for:

  • mysql
  • influxdb
  • php-fpm (including the Symfony application)
  • phpmyadmin
  • nginx

Everything is configured in .env.

There exist multiple persistent (shared) volumes:

  • symfony mapping to /var/www/symfony for the ClusterCockpit source tree
  • sql mapping to /var/lib/mysql
  • influxdb/data mapping to /var/lib/influxdb2
  • influxdb/config mapping to /etc//influxdb2
  • logs/nginx mapping to /var/log/nginx
  • logs/symfony mapping to /var/www/symfony/var/log

The containers are build and started using the command:

docker compose up

Desired modes for the future are:

  • Demo: Includes everything to try out ClusterCockpit including initial Database Fixtures. No SSL and no reverse Proxy.
  • Develop: Only includes all external components of ClusterCockpit. A functional PHP environment and the ClusterCockpit source must be maintained on host machine.
  • Production: Includes everything to run ClusterCockpit in a Production environment including SSL and traefic reverse proxy and container orchestration.

TODOS (There are probably a lot more!):

  • Some of the Volume directories need to be created first, others (influxdb) not
  • The main problem is currently the checkout of the ClusterCockpit tree to the existing directory /var/www/symfony, the directory is non-empty. Maybe because of caching
  • ClusterCockpit is at the moment still using the influxDB V1 API, the InfluxDB container is already V2
  • For a running demo database fixtures for MySQL and InfluxDB are missing