<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Posts on goroot</title>
		<link>https://blog.goroot.de/posts/</link>
		<description>Recent content in Posts on goroot</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 04 Dec 2021 14:28:10 +0100</lastBuildDate>
		
			<atom:link href="https://blog.goroot.de/posts/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Automated tasmota backups</title>
				<link>https://blog.goroot.de/post/automated-tasmota-backup/</link>
				<pubDate>Sat, 04 Dec 2021 14:28:10 +0100</pubDate>
				<guid>https://blog.goroot.de/post/automated-tasmota-backup/</guid>
				<description>&lt;p&gt;My smart home heavily relies on &lt;a href=&#34;http://tasmota.github.io&#34; rel=&#34;noopener&#34;&gt;tasmota&lt;/a&gt;&lt;a class=&#34;arch&#34; href=&#34;https://web.archive.org/web/20211204/http://tasmota.github.io&#34;&#xA;       title=&#34;Archived on 2021-12-04&#34;&#xA;       rel=&#34;nofollow noopener&#34;&gt;[arch]&lt;/a&gt; powered smart devices to work properly. While the tasmota software itself is rock stable and barely leads to any downtimes, the hardware it is running on isn&amp;rsquo;t quite. What do you do if you don&amp;rsquo;t have any tasmota backup and the device breaks? Would you be able to restore the configuration of dozens or even hundreds of devices just by remembering?&lt;/p&gt;</description>
			</item>
			<item>
				<title>How to use Visual Studio Code on your iPad</title>
				<link>https://blog.goroot.de/post/How-to-use-Visual-Studio-Code-on-your-iPad/</link>
				<pubDate>Thu, 29 Jul 2021 13:19:52 +0100</pubDate>
				<guid>https://blog.goroot.de/post/How-to-use-Visual-Studio-Code-on-your-iPad/</guid>
				<description>&lt;p&gt;I recently came across the problem that when being on vacation I don’t have my main computer available.￼ I usually only go on vacation with a light weight set of IT equipment, which is in this case my iPad Pro and a few cables and chargers￼. This is a conscious decision since I don’t want to invest too much - in the best case no time at all - into sitting in front of my computer￼￼. How ever, there are situations where you need to do a quick fix: for example one of my websites breaking or any other service not running anymore￼. Even if this would be theoretically possible it is hard to fix these things on a smart phone without having an IDE like &lt;a href=&#34;https://code.visualstudio.com&#34; rel=&#34;noopener&#34;&gt;VSCode&lt;/a&gt;&lt;a class=&#34;arch&#34; href=&#34;https://web.archive.org/web/20210729/https://code.visualstudio.com&#34;&#xA;       title=&#34;Archived on 2021-07-29&#34;&#xA;       rel=&#34;nofollow noopener&#34;&gt;[arch]&lt;/a&gt; in place.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Presence detection: Bee in a box</title>
				<link>https://blog.goroot.de/post/presence-detection-bee-in-a-box/</link>
				<pubDate>Thu, 22 Jul 2021 21:31:21 +0100</pubDate>
				<guid>https://blog.goroot.de/post/presence-detection-bee-in-a-box/</guid>
				<description>&lt;p&gt;The &amp;lsquo;bee in a box&amp;rsquo; algorithm enables you to detect presence in a given area of your smart home. It will enable your smart home system to know whether in a given area anybody is present or not. No special sensors or other additional hardware is required to do so.&lt;/p&gt;&#xA;&lt;h2 id=&#34;bee-in-a-box-algorithm-the-theory&#34;&gt;Bee in a box algorithm: The theory&lt;/h2&gt;&#xA;&lt;p&gt;Imagine somebody handing you over a small box made out of cardboard. On the top side of the box, there is a yellow warning symbol &amp;lsquo;Warning: there might be a bee inside&amp;rsquo;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>ESP32 as BLE Gateway for Xiaomi Mijia BLE Temperature &amp; Humidity Sensor</title>
				<link>https://blog.goroot.de/post/esp32-ble-gateway/</link>
				<pubDate>Thu, 01 Jul 2021 14:37:30 +0100</pubDate>
				<guid>https://blog.goroot.de/post/esp32-ble-gateway/</guid>
				<description>&lt;h2 id=&#34;problem-statement&#34;&gt;Problem statement&lt;/h2&gt;&#xA;&lt;p&gt;&lt;del&gt;Too many unused BLE sensors, too much time during the COVID-19 lockdown - lets add more sensors! Just because we can&amp;hellip;&lt;/del&gt;&lt;/p&gt;&#xA;&lt;p&gt;No seriously. I struggled a lot with too much humidity in the air in several areas of my house. After having a hot shower in the bathroom, the humidity condensed at the window, increasing the risk for mold growth. In the basement where our food supplies are stored, we had issues with salt getting wet. And since I also own a &lt;a href=&#34;https://blog.goroot.de/post/tasmota-homeassistant-pH-measurement/&#34;&gt;reef-tank connected to my smart home system&lt;/a&gt; which cools the water using evaporation, the humidity in the living room is also a very interesting measurement. So wh&lt;/p&gt;</description>
			</item>
			<item>
				<title>Monitor the pH of your reef tank with Tasmota</title>
				<link>https://blog.goroot.de/post/tasmota-homeassistant-pH-measurement/</link>
				<pubDate>Mon, 01 Mar 2021 21:09:03 +0000</pubDate>
				<guid>https://blog.goroot.de/post/tasmota-homeassistant-pH-measurement/</guid>
				<description>&lt;p&gt;Monitoring water values of your fish tank is essential. To keep your reef-ecosystem alive, several dozens of water values need to be measured. This can be quite annoying to do that manually all the time. So I just started automating the measurement of them via &lt;a href=&#34;http://tasmota.github.io&#34; rel=&#34;noopener&#34;&gt;Tasmota&lt;/a&gt;&lt;a class=&#34;arch&#34; href=&#34;https://web.archive.org/web/20210301/http://tasmota.github.io&#34;&#xA;       title=&#34;Archived on 2021-03-01&#34;&#xA;       rel=&#34;nofollow noopener&#34;&gt;[arch]&lt;/a&gt;. One of the leading indicators for a fish tank is the pH level of the water. Measuring the pH level gives you a good indication for several other water values as well.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Network segregation: IoT vs NoT networks</title>
				<link>https://blog.goroot.de/post/network-segregation-IoT-vs-NoT/</link>
				<pubDate>Thu, 18 Feb 2021 17:32:40 +0100</pubDate>
				<guid>https://blog.goroot.de/post/network-segregation-IoT-vs-NoT/</guid>
				<description>&lt;p&gt;IoT devices became quite popular throughout the last years. Everything is connected, anytime. What sounds like a good idea, might actually result in a security hole in your network. As only the vendor knows what a device is actually doing, your IoT devices might bring some features with them that you don&amp;rsquo;t like.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-the-problem-with-my-iot-device&#34;&gt;What is the problem with my IoT device?&lt;/h2&gt;&#xA;&lt;p&gt;The short answer is: you own it, but you don&amp;rsquo;t control it. But&amp;hellip;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Unattended docker container updates</title>
				<link>https://blog.goroot.de/post/unattended-container-updates/</link>
				<pubDate>Sat, 13 Jul 2019 14:32:03 +0000</pubDate>
				<guid>https://blog.goroot.de/post/unattended-container-updates/</guid>
				<description>&lt;p&gt;To keep your container infrastructure up to date and therefore secure, there are two primary objectives that you need to achieve:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Keep the host‘s operating system up to date&lt;/li&gt;&#xA;&lt;li&gt;Keep the content of your containers up to date&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;h2 id=&#34;update-the-operating-system&#34;&gt;Update the operating system&lt;/h2&gt;&#xA;&lt;p&gt;Updating your operating system is quite straight forward. Just use the well known package managers to do the job for you. E.g. for Debian this would be as easy as running &lt;code&gt;apt-get update &amp;amp;&amp;amp; apt-get upgrade&lt;/code&gt; on a regular basis.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Using the cloud as panic room</title>
				<link>https://blog.goroot.de/post/automated-cloud-backup/</link>
				<pubDate>Sat, 03 Feb 2018 18:41:00 +0000</pubDate>
				<guid>https://blog.goroot.de/post/automated-cloud-backup/</guid>
				<description>&lt;p&gt;Time to do something about it, and also about all other scenarios that threaten your digital heritage. Can the cloud be the safe place to backup all your data? But doesn&amp;rsquo;t uploading backups to the cloud also mean that others might be able to access it? In this article we will show a disaster recovery concept that you can use to backup infinite data amounts: It is free, easy to set up, and bullet prove.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Docker Image Review: jwilder/nginx-proxy</title>
				<link>https://blog.goroot.de/post/docker-image-review-jwilder-nginx-proxy/</link>
				<pubDate>Mon, 29 Jan 2018 10:18:00 +0000</pubDate>
				<guid>https://blog.goroot.de/post/docker-image-review-jwilder-nginx-proxy/</guid>
				<description>&lt;p&gt;Ever wondered wether there is a good alternative for scenarios, where a full featured ingress proxy would be overkill? Here it comes:&#xA;&lt;code&gt;jwilder/nginx-proxy&lt;/code&gt;. The image can especially be useful when setting up an ingress concept for the first time. &lt;a href=&#34;https://www.nginx.com&#34; rel=&#34;noopener&#34;&gt;Nginx&lt;/a&gt;&lt;a class=&#34;arch&#34; href=&#34;https://web.archive.org/web/20180129/https://www.nginx.com&#34;&#xA;       title=&#34;Archived on 2018-01-29&#34;&#xA;       rel=&#34;nofollow noopener&#34;&gt;[arch]&lt;/a&gt; is well known in the world of classic server administration and web hosting. So why not use your familiar web server also in your containerised environment?&#xA;Compared to full featured ingress routers like &lt;a href=&#34;https://traefik.io&#34; rel=&#34;noopener&#34;&gt;Traefik&lt;/a&gt;&lt;a class=&#34;arch&#34; href=&#34;https://web.archive.org/web/20180129/https://traefik.io&#34;&#xA;       title=&#34;Archived on 2018-01-29&#34;&#xA;       rel=&#34;nofollow noopener&#34;&gt;[arch]&lt;/a&gt; the image enables you to reuse your existing know-how, and also some of your configurations. The concept of a ingress router is similar to a reverse proxy. It is to hide all other services behind a single container, as you would do with a reverse proxy. The advantages are obvious: You don&amp;rsquo;t have to care about things like Encryption or authentication for each and every service separately. It also gives you the possibility to do things like load-balancing or gathering statistics across all your services.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Docker containers are insecure</title>
				<link>https://blog.goroot.de/post/docker-containers-are-insecure/</link>
				<pubDate>Sun, 14 Jan 2018 12:12:00 +0000</pubDate>
				<guid>https://blog.goroot.de/post/docker-containers-are-insecure/</guid>
				<description>&lt;p&gt;Everybody knows how to keep a linux box updated. It is also common sense that running things in docker containers is more secure by definition. After all they isolate services from each other. So if you are running containers on a fully patched host, there should be no security holes at all. Not even close! Keeping containers up to date is a total different thing. That brings up the questions how to keep your containers up to date, and how to decide wether containerising is really worth it in your scenario.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Starting on a blank page</title>
				<link>https://blog.goroot.de/post/starting-on-a-blank-page/</link>
				<pubDate>Thu, 11 Jan 2018 17:48:00 +0000</pubDate>
				<guid>https://blog.goroot.de/post/starting-on-a-blank-page/</guid>
				<description>&lt;h2 id=&#34;a-little-bit-of-history&#34;&gt;A little bit of History&lt;/h2&gt;&#xA;&lt;p&gt;The blog initially started in 2014 and was online till late 2016. I primarily focused on Ham Radio and IoT content these days. These topics were appreciated by many readers. Nevertheless, the old blog had to come to an end as my interests also changed over time. I was simply not able (nor willing :-)) to invest the time necessary to write high quality articles on topics that are no longer my primary focus.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
