Boilerplate docker-compose scaffold for personal projects. Grep for "boilerplate" to match your setup.
For development, consider using docker-compose_dev.yml, it overlays your app sources as volumes and starts app_flask with the friendly debugger. Probably needs a docker-compose -f docker-compose_dev.yml run app_nodejs npm install to get your npm packages first tho.
Runs a standard nginx with /web/default.conf as its config, serving from /web/www. You'll need to change the localhost in there to your hostname.
It bumps any plaintext traffic to HTTPS and forwards app traffic to the app servers.
The supplied cert.pem and key.pem are self-signed for localhost. The default.conf config shares the certbot_challenge directory which allows for manual-mode certbot actions, such as
sudo certbot --manual --agree-tos -d yourdomain certonly
This will pause and ask you to place a nonce in a nonce-named file reachable as http://yourdomain/.well-known/acme-challenge/nonce-named-file. You can create this file in certbot_challenge/.well-known/acme-challenge/ and continue with certbot. When it finishes, you can overwrite cert.pem with the resulting fullchain.pem, and key.pem with privkey.pem, both from whereever certbot placed them (likely /etc/letscenrypt/live/yourdomain/), and docker-compose restart web.
A placeholder flask(_restful) app. Any calls will kick off the worker, see below.
A placeholder nodejs/express app.
Runs a standard MySQL as UTF-8 as possible, with:
/envcontaining the auth credentials./db/content/as its/var/lib/mysql./db/backups/where it saved/loads its backups (see backups below)./db/entrypoint/where it looks for first-run SQL and shell scripts (see MySQL docker docs)./envcontaining the auth credentials.
/scripts/db_backup.sh dumps the MySQL contents to a timestamped file in /db/backups/, and returns the full path to it for your cronning pleasure. TODO mysql prints a warning first, so tail the output.
/scripts/db_restore.sh takes a backup's filename (which you need to place in /db/backups/ first) and reloads the database from that.
/scripts/db_shell.sh loads up a MySQL shell within the running db instance.
A standard Redis.
A placeholder worker to handle longer-living stuff (like sending mails) asyncly. Dies randomly so that the retry mechanism kicks in.
We had fucking Plan9 and now we're dealing with this.