| title |
|---|
Docker Deployment |
Kevin Turner Aug 2022
Square Events now builds docker images when PRs are merged with mainor manually via workflow-dispatch.
If the repo is checked out on a machine with docker and docker-compose installed then the app can be started with (using PGL as an example).
What was the config/local.js for each instance is now stored in a GitHub Actions Secret.
./docker.sh -a up -u -t pgl -p 1337
./docker.sh -a up -u -n sails-events-test -t pgl_test -p 1338
The -t option indicates the tag of the docker image. So you can see the images here packages where you can see that the image tag takes the form <tag>-latest.
The -u switch updates the local image from the repository. Obviously it can be left off if need be.
To stop the container run ./docker.sh -a down -n <sails-events or sails-events-test>
In order to use the command you have to login to ghcr.io using a PAT as a password - so you need permission to the kpturner repositories:
docker login ghcr.io/kpturner
Run the deploy workflow in GitHub or
SSH to the host and run ./docker.sh -a up -u -n <sails-events or sails-events-test> -t <tag> -p <port>
Although the docker container has its own version of node and redis it still depends on mysql and its database being provided externally (usually through Plesk) as well as the email service provider.
In some cases the application may not be able to access the MySql database. These are the things to check:
The MySql config is bound to all the interfaces:
bind-address = * in /etc/mysql/my.cnf
Check the subnet of the docker container:
docker network ls
docker network inspect <name>_default
Sort out the firewall
ufw allow from 192.168.0.0/16 or whatever subnet you find for the container.
ufw reload
Once docker is used for an instance its service should be stopped and disabled: sudo systemctl disable <SERVICE_NAME>