luke.b//blog

< back to logs after before

Currently, I can deploy a new app and the infrastructure for it in a single commit. Pretty dope. BUT, want I really want is for my apps to be built and/or run within docker containers.

At the moment, I think keeping the build.sh build scripts allows for some more flexible deployment of various things, e.g. sending an email out when my blog updates, restarting the nginx docker image when the config changes etc. So build.sh is here to stay.

Some of these build.sh however would be much better off building docker images and running them in such a way that they can share volumes. The simplest way to achieve this is I think to use docker-compose, which I am already using for the nginx reverse proxy.

So, next steps to bring dockerised auto deployment closer to reality:

  • rewrite blog building script as a Dockerfile
  • expose built static files using a docker volume, shared with the nginx container
  • repeat for all apps

In some cases, I will try to reuse common build steps of apps - e.g. a few apps of mine are built using Parcel, so I can use a single Dockerfile for those.

But not now it’s late I should be asleep D: