Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer’s view in any way.


posted on March 1, 2020 | tags: [ continuous deployment, planning, projects ]
main post image
Back and forth discussion of relevant topics.

"History is merely a list of surprises. It can only prepare us to be surprised yet again."

-- Kurt Vonnegut

Post from my iPad

I had been meaning to make my blog site more bloggable. I wanted to really be able to edit some markup on my iPad, grab and resize a few images and get it to my site. On my MBP, I run the Jekyll / Grunt toolchain. This compiles the site, compiles the LESS styles and JavaScript. It also minifies these assets and compresses the images. I am not able to do this yet on the iPad, but I thought maybe a hosted Docker container could do it.

Basically, I need a container in the cloud that can run the toolchain. Firstly, checkout my source after I push to my Github repo. Then bundle install any tools, e.g. Jekyll 4.0. Build will use the _config.yml and compile the source. Push to my repo deployment branch and let Azure pull the code into the app service.

So what to use to do that? AWS containers? Maybe, maybe check that out sometime. But I decided to take a look at Github Actions.

I found a Jekyll action and was able to create a workflow that runs on every push. Right now, all but minification and image compression is in place. Posting from my iPad now, hopefully, I'll be a bit more productive.




Future Engineers




Apps and Games




Blog Plan