<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Static Sites on App Coding</title>
    <link>https://appcoding.com/tags/static-sites/</link>
    <description>Recent content in Static Sites on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/static-sites/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy: A Small Go Web Server and Reverse Proxy That Explains Every Routing Decision</title>
      <link>https://appcoding.com/bareproxy-a-small-go-web-server-and-reverse-proxy-that-explains-every-routing-decision/</link>
      <pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/bareproxy-a-small-go-web-server-and-reverse-proxy-that-explains-every-routing-decision/</guid>
      <description>&lt;p&gt;Most sites run a thin slice of nginx in front of their application: TLS termination, serving static files from a folder, a couple of routes to a backend service, health checks, and the occasional reload. The configuration grows anyway, one regular expression at a time, until nobody is quite sure which block handles a given URL, and a change that looks safe to one person breaks something in production that another person didn&amp;rsquo;t know existed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
