Triggering Docker builds with an AWS IoT Button Not long ago GitHub and AWS together cross promoted a blog post about triggering new releases in GitHub by pressing an AWS IoT button. This new process got me thinking about how we can use an AWS IoT button together with Docker. After some research and jotting down my thoughts I had the ah-ha moment. What transpired after is a new way to think about how we can use IoT.
Deploying new containers has become ridiculously easy (In a good way). Once containers are running, it is even easier to scale. Doubling or even tripling the number of running containers can occur with a simple keystroke but can your container infrastructure handle it? Much like cars driving on a freeway. All the cars have different shapes, sizes, and performance. Cars are limited to the capacity of the road.
Grafana released v5.0 at GrafanaCon last week. It is a significant update packed with mouth-watering features. I’ve been testing the beta for quite some time and was very impressed with the maturity already in Beta. Most people will notice the New Dashboard Engine, UX, and themes as prominent visual updates. However, down the list of features which to be honest, I missed the first few times reading the release notes is an essential feature: Provisioning from Configuration.
Cryptocurrency Tracker Dashboard The Crypto craze has not hit full saturation until I release some tool to monitor it. Since I enjoy building monitoring projects, I felt it was the right time to re-purpose the Docker Prometheus stack for something even more significant. Enter stage right, Monitoring Cryptocurrencies. I happen to live in what is called Crypto Valley, Switzerland. We have more Crypto startups per-capita than anywhere else in the world.
The 56K.Cloud Automated Website It is an Automated static generated website to be precise. Wow, now that is a mouth full. It sounds much more complicated than it is. Our website’s goal is to showcase our DevOps skills and passion. We chose a toolset that enables us to deliver our content via CI/CD (Continuous Integration / Continuous Delivery). We decided on four base requirements: Maintained by Git Stored in GitLab Utilize a static site generator Automated deployments Netlify to the rescue We selected Netlify as the platform to deliver 56K.