<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>caddy on Cavelab</title>
    <link>https://www.cavelab.dev/tags/caddy/</link>
    <description>Recent content in caddy on Cavelab</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Thomas Jensen</copyright>
    <lastBuildDate>Tue, 16 Jun 2026 22:54:21 +0200</lastBuildDate>
	  <atom:link href="https://www.cavelab.dev/tags/caddy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Securing Home Assistant API access for Dakboard — with Caddy</title>
      <link>https://www.cavelab.dev/posts/secure-home-assistant-api-caddy/</link>
      <pubDate>Tue, 16 Jun 2026 22:54:21 +0200</pubDate>
      <guid>https://www.cavelab.dev/posts/secure-home-assistant-api-caddy/</guid>
      <description>&lt;img src=&#34;https://www.cavelab.dev/posts/secure-home-assistant-api-caddy/cover.jpg&#34;/&gt; &lt;p&gt;Back in 2021 I added &lt;a href=&#34;https://www.cavelab.dev/posts/dakboard-data-from-home-assistant/&#34;&gt;Home Assistant sensor data&lt;/a&gt; to our &lt;a href=&#34;https://www.cavelab.dev/posts/raspberry-pi-dakboard-display/&#34;&gt;Dakboard monitor&lt;/a&gt;. But I did so using a long-lived access token directly on the Dakboard blocks — which is not great for a couple of reasons:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Tokens have no access scope, meaning they grant full admin access to everything&lt;/li&gt;&#xA;&lt;li&gt;The token was stored on Dakboard&amp;rsquo;s servers&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;I want Dakboard to be able to pull data from my locally hosted Home Assistant, but I&amp;rsquo;d like to restrict access.&lt;/p&gt;&#xA;&lt;p&gt;I did this using Caddy as a reverse proxy 🤓&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
