This is an unofficial Docker image for Cloudlog, a PHP based amateur radio logging software created by 2M0SQL.
I created it after the team behind Cloudlog decided to rescind any support for Docker and no longer updates the official image. The intent of this image is to also default certain features the official image never had, such as enabling mod_rewrite or cronjobs.
- Based on php:8.2-apache,
- mod_rewrite enabled,
- No "/index.php/" in the URL,
- "Production" mode enabled by default,
- Comes with (most) cronjobs out-of-the-box.
2.6.13
Whenever this image is updated post-install, the version number will not update in Cloudlog under "Debug Information" and "Version Info". This is due to a slight oddity with Cloudlog since the version number is a value stored in the MySQL database.
You can manually adjust the version number using phpMyAdmin (you can find the version number in the table "options"), however, adjusting this value is purely cosmetic and has no influence on functionality (other than displaying the wrong changelog when opening "Version Info").
IMPORTANT: MAKE SURE TO CHANGE THE MYSQL PASSWORD!
version: '3'
services:
cloudlog-main:
image: jk13xyz/cloudlog:latest
container_name: cloudlog-main
depends_on:
- cloudlog-mysql
volumes:
- cloudlog-config:/var/www/html/application/config
- cloudlog-uploads:/var/www/html/uploads
- cloudlog-images:/var/www/html/images
ports:
- "7373:80"
restart: unless-stopped
cloudlog-mysql:
image: mysql:latest
container_name: cloudlog-mysql
environment:
MYSQL_RANDOM_ROOT_PASSWORD: yes
MYSQL_DATABASE: cloudlog
MYSQL_USER: cloudlog
MYSQL_PASSWORD: "STRONG_PASSWORD"
volumes:
- cloudlog-dbdata:/var/lib/mysql
restart: unless-stopped
cloudlog-phpmyadmin:
image: phpmyadmin:latest
container_name: cloudlog-phpmyadmin
depends_on:
- cloudlog-mysql
environment:
PMA_HOST: cloudlog-mysql
PMA_PORT: 3306
PMA_USER: cloudlog
PMA_PASSWORD: "STRONG_PASSWORD"
restart: unless-stopped
ports:
- "7374:80"
volumes:
cloudlog-dbdata:
cloudlog-config:
cloudlog-uploads:
cloudlog-images:docker volume create cloudlog-dbdata && \
docker volume create cloudlog-config && \
docker volume create cloudlog-images && \
docker volume create cloudlog-uploads
docker run -d \
--name cloudlog-main \
-v cloudlog-config:/var/www/html/application/config \
-v cloudlog-backup:/var/www/html/application/backup \
-v cloudlog-images:/var/www/html/images \
-v cloudlog-uploads:/var/www/html/uploads \
-v cloudlog-crontab:/var/www/html/crontab \
-p 7373:80 \
--restart unless-stopped \
jk13xyz/cloudlog:latest
docker run -d \
--name cloudlog-mysql \
-e MYSQL_RANDOM_ROOT_PASSWORD=yes \
-e MYSQL_DATABASE=cloudlog \
-e MYSQL_USER=cloudlog \
-e MYSQL_PASSWORD="STRONG_PASSWORD" \
-v cloudlog-dbdata:/var/lib/mysql \
--restart unless-stopped \
mysql:latest
docker run -d \
--name cloudlog-phpmyadmin \
-e PMA_HOST=cloudlog-mysql \
-e PMA_PORT=3306 \
-e PMA_USER=cloudlog \
-e PMA_PASSWORD="STRONG_PASSWORD" \
--restart unless-stopped \
-p 7374:80 \
phpmyadmin:latest-
Open Cloudlog on your host (e.g. localhost:7373).
-
Change the Locator and adjust the URL, if necessary. You can leave "Directory" usually empty.
-
Enter the database credentials
- Host: cloudlog-mysql
- User: cloudlod
- Database: cloudlog
Use the password you choose when running the docker.
-
Hit install.
- If Cloudlog installs into a blank screen, open the base URL
The following cronjobs are set by default through the Dockerfile They don't need to be manually enabled. They can be updated, but this is a hassle. I use these settings because they made the most sense to me. The spacing is done to ensure the scripts don't run concurrently and cause time-outs.
The set cronjobs and runtimes are:
Every day at 00:00 and 12:00
Every day at 00:10 and 12:10
Every day at 00:20 and 12:20
Every day at 00:30 and 12:30
Every day at 00:40 and 12:40
Every day at 01:00
Every day at 01:10
Every Monday at 01:20
On the 1st of every month at 02:00
On the 1st of every month at 02:10
On the 1st of every month at 02:20
On the 1st of every month at 03:00
While the ADIF file can be useful, it's crucial to backup the MySQL database in regular intervals as well. This is even more important when you use more than just one station location and/or users.
I have ready-made scripts for backup available at jk13xyz/backup-scripts.
This script is especially helpful when you run more than one MySQL container.
Alternatively, you can use the following command to trigger a database dump manually:
docker exec cloudlog-mysql /bin/bash -c 'mysqldump --user cloudlog --password=YOUR_PASSWORD cloudlog' > /your/path/to/cloudlog.sqlYou can easily turn this command into a cronjob. If you have crontab installed, simply use this command to run a cronjob daily at 06:00:
echo "0 6 * * * docker exec cloudlog-mysql /bin/sh -c 'mysqldump --user cloudlog --password=YOUR_PASSWORD cloudlog' > /your/path/to/cloudlog.sql" >> /etc/crontabWith that set, keep the 3-2-1 backup rule (3 copies, 2 different media, 1 copy off-site) in mind. Any backup should also at the very least keep the cloudlog-config backup in mind. If you use functionalities such as displaying your QSL cards, also include cloudlog-images.
Please note, this is primarily for my own setup. Feel free to use it (it should work fine). If you find issues, report them on my Github. However, I don't guarantee any support.
-
This Docker:
-
Cloudlog: