-
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.xml
86 lines (72 loc) · 7.01 KB
/
index.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Helix's Blog</title>
<link>https://helixspiral.github.io/</link>
<description>Recent content on Helix's Blog</description>
<generator>Hugo -- gohugo.io</generator>
<language>en-us</language>
<lastBuildDate>Fri, 19 Jan 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://helixspiral.github.io/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>Chicken Coop Tech</title>
<link>https://helixspiral.github.io/posts/2024-01-19-chicken-coop-tech/</link>
<pubDate>Fri, 19 Jan 2024 00:00:00 +0000</pubDate>
<guid>https://helixspiral.github.io/posts/2024-01-19-chicken-coop-tech/</guid>
<description>Overview Over the end of year 2023 Holidays I had a vacation and started working on revamping some tech for my chicken coop. This blog post is going to detail what we had initially, what I&rsquo;m building, and some future ideas for the chicken tech.
Equipment/Software Used Original Helium Hotspot - Any official Helium Hotspot1 or home-built Data-Only2 hotspot will work SenseCAP 2103 (2)3 - LoRaWAN Temp, Humidity, and CO2 Sensor Raspberry PI 4b 8GB (2) - Local k8s cluster running in my home Helium Console4 - Helium Network console provided by the Helium Foundation, but any Helium-compatible console will work SenseCAP-Decoder5 - Javascript function for decoding 210X sensors provided by SenseCAP.</description>
</item>
<item>
<title>Environment Configurable vs Environment Agnostic Applications</title>
<link>https://helixspiral.github.io/posts/2023-09-27-environment-configurable-vs-environment-agnostic-applications/</link>
<pubDate>Wed, 27 Sep 2023 00:00:00 +0000</pubDate>
<guid>https://helixspiral.github.io/posts/2023-09-27-environment-configurable-vs-environment-agnostic-applications/</guid>
<description>Introduction As a member of an operations team you want things to be easy, you want things to &ldquo;just work&rdquo; the same way in a testing environment as they do in a production one. In this post we&rsquo;ll cover applications that need to be configured, and how to remove those needed configurations in favor of an application that &ldquo;just works&rdquo;.
Environment configurable Here is our example environment configurable application:
package main import ( &#34;fmt&#34; &#34;os&#34; &#34;github.</description>
</item>
<item>
<title>Multi-arch Docker builds with Rust</title>
<link>https://helixspiral.github.io/posts/2023-06-16-rust-multiarch-docker/</link>
<pubDate>Fri, 16 Jun 2023 00:00:00 +0000</pubDate>
<guid>https://helixspiral.github.io/posts/2023-06-16-rust-multiarch-docker/</guid>
<description>Introduction I&rsquo;ve recently been playing with some Rust projects, and one of the biggest struggles I had was getting a small platform agnostic Docker image that I could use to build any platform using docker buildx.
The code I wrote a very small program that spits out a random number along with the current architecture to use as an sample for our Docker work.
use rand::Rng; use current_platform::CURRENT_PLATFORM; fn main() { let mut rng = rand::thread_rng(); let r_num: u8 = rng.</description>
</item>
<item>
<title>Astronomy Picture of the Day Notification Service</title>
<link>https://helixspiral.github.io/posts/2022-07-26-astronomy-picture-of-the-day-notification-service/</link>
<pubDate>Tue, 26 Jul 2022 00:00:00 +0000</pubDate>
<guid>https://helixspiral.github.io/posts/2022-07-26-astronomy-picture-of-the-day-notification-service/</guid>
<description>Overview In this blog we&rsquo;ll cover how the Astronomy Picture of the Day microservices are built and deployed with Docker and Kubernetes, and how to deploy the lightweight MQTT broker Mosquitto.
This is a follow up to my previous blog post System Scalability and Microservices with some additional information.
Requirements Docker installed locally Working Kubernetes cluster Helm installed GitHub repositories All of the code relating to this blog post can be found at the following links and is released under the GPL-3.</description>
</item>
<item>
<title>System Scalability and Microservices</title>
<link>https://helixspiral.github.io/posts/2022-02-28-system-scalability-and-microservices/</link>
<pubDate>Mon, 28 Feb 2022 00:00:00 +0000</pubDate>
<guid>https://helixspiral.github.io/posts/2022-02-28-system-scalability-and-microservices/</guid>
<description>Overview This blog will talk about system scalability with relation to microservices and how a monolithic application would be less desired in this example.
GitHub repositories All of the code relating to this blog post can be found at the following links and is released under the GPL-3.0 license, with the exception of the official NASA api which is released under the Apache-2.0 license.
Official NASA APOD API - The official NASA API for getting the Astronomy Picture of the Day.</description>
</item>
<item>
<title>Ensuring backwards compatibility in deployments by leveraging git tags</title>
<link>https://helixspiral.github.io/posts/2021-04-02-using-git-tags-to-ensure-deployment-backwards-compability/</link>
<pubDate>Fri, 02 Apr 2021 00:00:00 +0000</pubDate>
<guid>https://helixspiral.github.io/posts/2021-04-02-using-git-tags-to-ensure-deployment-backwards-compability/</guid>
<description>Overview I recently came across a blog post on injecting variables into Golang at build time and that gave me the idea for this blog post. Automating versioning and ensuring backwards compatibility.
GitHub repository and sample application You can find the code for this application here, on my GitHub
Git tags and versioning This blog post assumes some basic understanding of the git version control system. For anyone new to it you can probably get by with thinking that commits are incremental changes to the software and tags are user-created labels that reference a specific commit.</description>
</item>
<item>
<title>Automating Kubernetes with Saltstack</title>
<link>https://helixspiral.github.io/posts/2020-10-13-automating-kubernetes-with-saltstack/</link>
<pubDate>Tue, 13 Oct 2020 00:00:00 +0000</pubDate>
<guid>https://helixspiral.github.io/posts/2020-10-13-automating-kubernetes-with-saltstack/</guid>
<description>Overview My goal for this project was to setup and manage a Kubernetes cluster using Saltstack, the idea being that since I wanted to learn them both if I could automate the setup of the cluster I&rsquo;d be killing two birds with one stone.
I found a few good blog posts on this but all the ones I found lacked the level of automation I was looking for, some had hard coded values and others had manual commands needing to be run on the minions.</description>
</item>
</channel>
</rss>