Reverse-proxy yourself to the host

This is a follow-up post to the one I’ve written last week. I’ve showed there how to leverage Docker and Let’s Encrypt for easier HTTPS on localhost but that solution required developing your app inside a container. I personally prefer that option but sometimes the tooling is not so well suited for work inside container (e.g. webpack + Docker for Windows). For that we need to take a little different route.

Reverse-proxy yourself to localhost with SSL/TLS

Some time ago Scott Hanselman described how to setup self-signed certificates for localhost using dotnet dev-certs. Having SSL on localhost is, for me, a must-have since we all want to have our dev env resemble production as much as possible. The approach Scott showed is great but it might be a little bit hard to use on Linux. On Linux-based systems there are multiple libraries, multiple (probably embedded) stores and hundreds of options to configure all of this. I’ll show you an another approach that will allow to develop apps locally with full SSL/TLS and nice addresses.

FAKE your way to ASP.NET Core on Azure WebApps, part 3 - The Solution, Again

Deploying sites to Azure should be relatively easy. And it is, provided that you deploy from Visual Studio (and this is wrong on so many levels…). But if you want to automate things, well… You’re in a bad position.

I’ve tried to develop a solution last time. It works, but not always. I’ve finally got around to improve it and force it to work more frequently, but this time I am not going to say that it will be flawless or will ever be.

FAKE your way to ASP.NET Core on Azure WebApps, part 2 - The Solution

Last time I talked about an easy problem of deploying .NET Core programs to Azure WebApps (or, well, any other app that can run there). As it turned out, it isn’t that easy, but let’s face the truth - there are far more complicated things in IT and we shouldn’t spend too much time talking about simple deployments. So let’s get started!

FAKE your way to ASP.NET Core on Azure WebApps, part 1 - The Problem

A year has passed and times have changed, but my love for programming will always be the same… OK, enough. That opening didn’t quite work out, right? ;)

Recently, I’ve been extensively working with .NET Core apps (YES! I can finally ditch Visual Studio!). I’m used to working with technologies that have unstable tooling (Hey! I’m talking to you, @drunkvs!), so it was rather pleasant experience. However, there is one question that I couldn’t find an answer to - how to automatically deploy these things into the wild?