In many CI/CD scenarios it’s necessary to adjust the build, test or deployment process depending on which GIT branch has triggered the pipeline. In our case we build lots of Angular apps automatically with their desired target environment, e.g.
ng build --configuration="production" or
ng build --configuration="staging"
depending on where the artifact should be deployed afterwards. This can be achieved by adding some YAML that looks like this:
Continue reading Branch Name as Variable in Azure DevOps Pipelines with YAML
One of the major reasons for utilizing an Azure Iot Edge Gateway is to connect devices to the internet that can’t directly establish a connection themselves. A very common case are Bluetooth beacons, that can provide sensor data through a Bluetooth Low Energy (BLE) connection but are not able to send this information directly to an Azure IoT Hub.
For this scenario a bridge or gateway is required to create an IoT message from the Bluetooth payload. This is called Protocol Translation and can be achieved by creating a custom IoT Edge Module. Interestingly enough Microsoft has still not managed to provide a sample or best practice on how to do this with the IoT Edge Runtime V2, so here’s how we did it in our latest IoT project.
Continue reading Bluetooth Low Energy BLE devices with Azure IoT Edge
In a lot of IoT solutions Gateways play important roles. They can help connect downstream devices to the Cloud through Access Points, provide offline caching capabilities or translate protocols that are not suitable for direct internet access like Bluetooth. With Azure IoT Edge Microsoft has a great product for these kinds of devices which allows you to deploy custom docker modules for different kinds of tasks like evaluating data on the Edge before sending everything to a connected Azure IoT Hub.
Continue reading Azure IoT Edge Identity Translation: Getting Started
TLDR: npm install can update your npm packages potentially destabilizing your build process by using untested dependency versions. Use npm ci instead!
If you’re like me you might have several node-based apps, nicely configured to be built and deployed using automatic build & release pipelines.
So one of the first things you’re probably doing in that build pipeline is installing all required dependencies from npm, with your process looking something like this:
Continue reading Stop using npm install in your CI/CD pipelines
In this post I will show you how to turn some dynamic data into a static website using a timer-triggered Azure Function (written in nodejs) & mustache with static website hosting for Azure Storage.
For this demo I’ll create a simple, personalized start page showing some headlines I grab from a WordPress site and also adding a few links I often use. There are certainly way more interesting and useful scenarios for this but it should help you get started with your own ideas.
Continue reading Building static websites with Azure Functions, mustache & Azure Storage
Currently I’m playing around with the new Static website hosting for Azure Storage feature which has recently been launched in public preview. This allows you to serve static web content (HTML, CSS, JS, images) directly from a dedicated blob directory inside Azure Storage without setting up any kind of web app or proxy function.
Continue reading Remember to set the Content Type when using Static website hosting for Azure Storage
We’re currently building an Angular 4 + Cordova app for Android and iOS. One big feature is the photo upload, which takes multiple images, displays a preview and uploads it to the server.
Continue reading CSS Background-Url Performance Issues (TIL)