There are many times when you need to get your client IP address: for application telemetry, for getting the client country or any other info you may need. Anyway, when you deploy a .Net Core app on AKS and you are using an NGINX ingress, that you didn’t explicitely configure, the IP address you will be receiving into your app may not be what you expected.

There are many times when you need to get your client IP address: for application telemetry, for getting the client country or any other info you may need. Anyway, when you deploy a .Net Core app on AKS and you are using an NGINX ingress, that you didn’t explicitely configure, the IP address you will be receiving into your app may not be what you expected.

This past May 19th, while I was watching the Static Web App Build presentation, I decided to do a test with HUGO to start again my blog after 5 years of silence.

TL;DR: Static Web Apps allows you to deploy static content with a custom domain and Azure Web Apps does the rest: creates a GitHub Action for continuous deployment, gives you an SSL certificate for your custom domain, does the global distribution and helps you with Azure Functions if you need to generate some content from an API. Best of all, it’s all for FREE, you even get a free SSL certificate for your site’s custom domain.

If you need to create and/or execute pipelines from another Azure DevOps (ADO) pipeline, there’s an ADO extension for the az CLI that will allow us to perform this task, but we will need some preparation steps before running it. Today it’s still a preview characteristic, so it may suffer some changes when reaching general availability.

The first thing you need to know is that there’s a difference between the pipeline definition file, a yaml file, and the actual pipeline that will run. This last one is a logical pointer to the first that is usually created within the web console, but you can also use the CLI or the API to create them.

Unifi deprecated their Network Video Recorder (NVR) in exchange for their new Unifi Protect system, and, for this last one, there’s no installer to deploy it in our own hardware, as you could do with the former Unifi Video. Now they only distribute it with their own hardware. We just bought a new big server for installing Home Assistant, NVR, the Unifi Controller, and some other applications for our local installation, so we didn’t want to buy more hardware that we didn’t really need. Today we will learn how to install the NVR and fix some installation issues, like the Java version you need to make it work inside Ubuntu 20.10.

There are many times when you need to get your client IP address: for application telemetry, for getting the client country or any other info you may need. Anyway, when you deploy a .Net Core app on AKS and you are using an NGINX ingress, that you didn’t explicitely configure, the IP address you will be receiving into your app may not be what you expected.

In the previous chapter, we assembled a Docker container to execute a service written in VB6. Today, we are going to use this container in a Kubernetes cluster deployed in Azure using the Azure Kubernetes Service.

Here it is, the first in a series of (4) 5 posts on how to make something new from old Windows Server Applications that you may have running on-premises wasting a lot of hardware and energy.

When you do an assessment of running applications in your Windows servers, as a best scenario, you may find some old web apps running on an IIS server that could be migrated using a semi-automated tool, but, in my experience, there are lots of not-so-edge cases that won’t be as easy as that. Recently, I stumbled on a TCP/IP server application written in VB6 that was running in a few hundred virtual machines. At first, you may think that this application does not deserve the effort and it would be better to do a complete rewrite. Well, on the one side, from a developer or operator point of view you are completely right, but, on the other side, from a business perspective it’s all about trade-offs, and you may not have the budget to build a new app from scratch. So, what if you could reduce the current solution cost by containerizing it, so you save in hardware, and use these savings to push for the rewrite of a new and modern solution? Let’s talk about it.

In the previous chapter, we assembled a Docker container to execute a service written in VB6. Today, we are going to use this container in a Kubernetes cluster deployed in Azure using the Azure Kubernetes Service.

Here it is, the first in a series of (4) 5 posts on how to make something new from old Windows Server Applications that you may have running on-premises wasting a lot of hardware and energy.

When you do an assessment of running applications in your Windows servers, as a best scenario, you may find some old web apps running on an IIS server that could be migrated using a semi-automated tool, but, in my experience, there are lots of not-so-edge cases that won’t be as easy as that. Recently, I stumbled on a TCP/IP server application written in VB6 that was running in a few hundred virtual machines. At first, you may think that this application does not deserve the effort and it would be better to do a complete rewrite. Well, on the one side, from a developer or operator point of view you are completely right, but, on the other side, from a business perspective it’s all about trade-offs, and you may not have the budget to build a new app from scratch. So, what if you could reduce the current solution cost by containerizing it, so you save in hardware, and use these savings to push for the rewrite of a new and modern solution? Let’s talk about it.

There are many times when you need to get your client IP address: for application telemetry, for getting the client country or any other info you may need. Anyway, when you deploy a .Net Core app on AKS and you are using an NGINX ingress, that you didn’t explicitely configure, the IP address you will be receiving into your app may not be what you expected.

In the previous chapter, we assembled a Docker container to execute a service written in VB6. Today, we are going to use this container in a Kubernetes cluster deployed in Azure using the Azure Kubernetes Service.

Here it is, the first in a series of (4) 5 posts on how to make something new from old Windows Server Applications that you may have running on-premises wasting a lot of hardware and energy.

When you do an assessment of running applications in your Windows servers, as a best scenario, you may find some old web apps running on an IIS server that could be migrated using a semi-automated tool, but, in my experience, there are lots of not-so-edge cases that won’t be as easy as that. Recently, I stumbled on a TCP/IP server application written in VB6 that was running in a few hundred virtual machines. At first, you may think that this application does not deserve the effort and it would be better to do a complete rewrite. Well, on the one side, from a developer or operator point of view you are completely right, but, on the other side, from a business perspective it’s all about trade-offs, and you may not have the budget to build a new app from scratch. So, what if you could reduce the current solution cost by containerizing it, so you save in hardware, and use these savings to push for the rewrite of a new and modern solution? Let’s talk about it.