Shawn Wildermuth


Tagged with GitHub

ASP.NET Core in Azure App Services' Docker Images - Part 3

Azure App Services In this last post in the series, i'll show you how to use GitHub Actions to automate when you want to push a new version of your container to your Azure App Service.

While you could do the same automation in a lot of other tools, the important idea here is that you want to automate it all.

This will be a three part series:


Github Actions for CI-CD

GitHub ActionsI've been lazy. It's true. I've been waiting to setup CI/CD for a long time on my own project websites. While I've used Appveyor and others before, I wanted something easier to manage in one place. That's why I choose Github Actions!

I was going to write a long walkthrough, but I figured it would be easier to show you. So I shot this quick video (ok, it's actually about 20 minutes) and edited it lightly so you can see all the problems I run into and how to fix them. Let me know if this is the kind of content you're interested in!

What do you think about GitHub Actions?


What Does the GitHub Registry Mean to Developers?

GitHubAs you might have heard, GitHub has created it's own package registry. On the face of it, it might just feel like an opportunity to get more 'buy-in' into using GitHub, but I think something else is going on.

While most people are focusing on the support in NPM for the GitHub registry, they're actually supporting a package repository for a handful of package services. These include Nuget, Ruby Gems, Maven, and Docker. Why are they doing this?

The biggest benefit for people already using GitHub is to be able to expose their code as packages directly in the same environment. This limits the number of steps involved.