<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github on Broderic Duncan</title><link>/tags/github/</link><description>Recent content in Github on Broderic Duncan</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright &amp;copy; 2025 😎</copyright><lastBuildDate>Fri, 05 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="/tags/github/index.xml" rel="self" type="application/rss+xml"/><item><title>Moving Off of Netlify</title><link>/post/moving-away-from-netlify/</link><pubDate>Fri, 05 Dec 2025 00:00:00 +0000</pubDate><guid>/post/moving-away-from-netlify/</guid><description>&lt;p&gt;Ever since I started this blog 3 years ago back in 2022 I&amp;rsquo;ve hosted it on Netlify. &lt;a href="/post/thoughts-on-hugo"&gt;Here is my first post whining about how difficult it was for me to set that up.&lt;/a&gt;. Looking back after having a better understanding of both Hugo and Netlify, my complaints are pretty dumb. I&amp;rsquo;ve learned from certain mistakes like using GitHub submodules unnecessarily and being able to read docs better.&lt;/p&gt;
&lt;p&gt;My newest complaint however is a bit more valid. I&amp;rsquo;ve been reading more and more regarding AI scrapers and was curious what kind of bot traffic my blog was receiving. So I go on Netlify and look around for logs. Can&amp;rsquo;t find any kind of access logs. Find out that Netlify does offer logs, however they are on their paid plan, and they do not provide really the level of detail compared to logs from like nginx. Since I already self host a VM running nginx, I decided I might as well throw that on it too. I&amp;rsquo;ve also starting building up monitoring for everything in my home lab. Lots of messing around with SNMP (I hate it) and &lt;a href="https://grafana.com/go/webinar/getting-started-with-grafana-lgtm-stack/"&gt;Grafana&amp;rsquo;s LGTM stack&lt;/a&gt;. My overall plan is to eventually create some kind of primitive NOC &amp;amp; SOC.&lt;/p&gt;</description></item></channel></rss>