<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nginx on Companionway</title>
    <link>https://www.companionway.net/tags/nginx/</link>
    <description>Recent content in Nginx on Companionway</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 05 Jun 2026 09:12:04 -0400</lastBuildDate>
    <atom:link href="https://www.companionway.net/tags/nginx/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Nginx Auth</title>
      <link>https://www.companionway.net/post/nginx_auth/</link>
      <pubDate>Fri, 05 Jun 2026 09:12:04 -0400</pubDate>
      <guid>https://www.companionway.net/post/nginx_auth/</guid>
      <description>Gatekeeping the Grid: Building a Secure Nginx Protected Subdirectory with HTTP Basic Auth When hosting a custom dashboard or a set of administrative tools on a private server, you don&#39;t always need a massive, database-backed user authentication system just to keep prying eyes out of your data. If your architecture is lean, the absolute most efficient approach is to let the web server itself handle the gatekeeping.&#xA;Using Nginx’s native basic authentication modules, you can isolate a specific subdirectory under your document root (like /admin or /private) and lock it down for a single user.</description>
    </item>
  </channel>
</rss>
