Introduction SigPlot is a plotting solution from LGS Innovations for web-based applications which we’ve used in previous demos of our own web UI, and the REDHAWK SDR group used in their RTL Demo App from a few years back. The library provides for a number of features and plugins that can make for many plot […]
A common misconception about REDHAWK and GNURadio is that they’re at odds with one another, perhaps enemies. The truth is each can support the other with a little bit of integration effort. In this post, we’ll be digging more into the details and usage of GNURadio-REDHAWK, which we discussed and released during the GNURadio Convention in 2017.
In the previous posts, we’ve covered how to set up trusted SSL for internal services, then how to enable HTTPS and Container Repository features on a GitLab server, and finally how to add Runners to your server. In this case, we’ll focus on a Docker runner.
In the previous two posts, we covered first setting up SSL registration and automated maintenance using a Docker container from LinuxServer.io for Let’s Encrypt’s services, and then followed it up with enabling encrypted HTTPS and Container Repository on a GitLab server. So what’s next on the list for fully-functional Continuous Integration (CI)? Runners.
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.