infrastructure

Intro I wanted to play a little with Docker Compose so I created a little PoC that had the usual components of a web application: a frontend, a backend and a supporting database. Sample code to follow along here. Sample overview As I was just looking for the simplest thing just to make all the bits work together, I whipped out a pretty stupid scenario. The application basically lists some counters and increments each one as it’s selected....

Just added a new video, talking about the blog’s move from WordPress (and all that infrastructure I talked about in these series of posts) to a static site, generated using Jekyll and hosted using Netlify. A side note that I forgot to mention in the video: when using Jekyll, we need to set the environment variable JEKYLL_ENV to production, or stuff like Google Analytics and Disqus comments won’t work, as it’s disabled by default unless we’re in production....

To finish up this series of posts I’ll just go by a couple of extra things I needed to do to get the, mostly functional by now, site to work better. The main points are: Getting some certificates to get the site working on https. Using a mail server to overcome an issue with WordPress running on Docker. Get the site on HTTPS Everybody likes (or should) when you go to a web site and it uses HTTPS, even more so when there are private stuff going down the wire (like user credentials)....

This post will focus on installing the Docker engine and then running the applications we need to make the blog work as Docker containers. I’m not the best to explain all about Docker, so I’ll focus on what I needed to do to get the blog running. If you really want to learn about Docker there are lots of good resources out there, starting with Docker’s own documentation (which I used a lot)....

So this post is gonna be more of a “getting started with a virtual machine in a cloud provider” sort of thing, not very advanced, just a simple step by step guide for someone who never did it. Cloud Providers Like I said in the intro to this series of posts, I’m using Linode mainly for it being slightly cheaper than Digital Ocean (referred as DO from now on) which I was using before it....

So I guess a good article to begin with would be to explain how I got this site up. Even more fitting is it has nothing to do with .NET, which you would expect would be on the debut article around this parts (rest assured those will come like a stampede :) ). So, let me start by summarize how this thing is working: The server is a Linode [1] virtual machine....