I've used my Synology NAS for some time now - about two years and counting, and it's been a great tool to backup information locally (e.g. from my phones or shared computers). Then, I got to thinking - it's pretty much a mini-computer. It has a quad-core 1.4Ghz CPU, a whopping 2GB RAM, and _plenty_ of storage. I can do more with it than just use it for occasional data dumps. That is - I could use it for frequent data dumps.
As I was fiddling with some automation scenarios at home, I thought of putting the Synology Network Attached Storage (NAS) to good use. That is, in addition to all the photo backup stuff it's already doing. At the end of last year, I wrote a blog post about building a simple system to maintain evergreen notes, based on Hugo, Docker, and, well, that's it - there are only Markdown files in the mix. Evergreen notes in this context are nothing other than a personal Wikipedia of sorts.
Some of the more traditional approaches to taking digital notes work quite well in 99% of cases - I think most of the tools on the market are doing a marvelous job. But I often caught myself needing something more, specifically for notes that I wanted to write once and frequently refer to later (e.g. details about specific projects that don't change often).
Today, we are once again talking about builds, and pushing for more automation in your software creation process. Before we get started, make sure that you have the following pre-requisites handy: A Visual Studio Team Services account. Those are free. An Azure account. Those can be free for trial (1). Installed Docker. Installed Azure CLI. Pretty much all of the code and descriptions described below can be followed on macOS, Windows or Linux, as most of them will be done within the web interface, through your favorite web browser.
If you read one of the latest Ars Technica pieces about how Microsoft renewed its strategy on embracing developers across the board, you might've stumbled across this little tidbit about code sample testing.