As discussed in the previous guide, we used Let’s Encrypt to get legitimate SSL certificates for valid, external domains, and then mapped all of it internally to our own locally-hosted services via DNS. And of course, everything that needs to be maintained periodically is completely automated — a well-oiled machine.
If you’re unfamiliar, Let’s Encrypt allows you to register multiple domains and subdomains to get a valid SSL certificate (i.e., valid as in signed by a trusted third party Certificate Authority, CA) for encrypting your services. They also provide a utility for persistently maintaining the registration over time so that your certificates are always valid.
Some Quick History The last time we demoed bringing the B205mini into REDHAWK, it was again using Docker to containerize an environment conducive for a more recent version of UHD. Back then, we were working in different constraints: REDHAWK 2.0.2 CentOS 6.7 64-bit One constraint required the other, and the other required an older version […]
Introduction Last week we pushed out a flurry of updates that have changed, at least for us, the way that we can prototype and test entire REDHAWK systems. It is called Docker-REDHAWK(pre-built at Docker Hub). I’m going to start by assuming that you’re familiar with Docker from at least a high-level (images derived from layers […]
Introduction Over the past couple of years we have showcased a few demos where we use Docker images and containers to stand up various capabilities, like utilizing the latest version of UHD for our Ettus Research USRP hardware like the B205mini USB3 transceiver. So recently, we decided to revamp the capability to make it even […]