<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Drew Fisher</title>
    <description>The latest articles on DEV Community by Drew Fisher (@wired_fisher).</description>
    <link>https://dev.to/wired_fisher</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4210923%2F783095d6-fcdd-473f-b606-498e332b9364.jpg</url>
      <title>DEV Community: Drew Fisher</title>
      <link>https://dev.to/wired_fisher</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/wired_fisher"/>
    <language>en</language>
    <item>
      <title>Moving a side project to Cloud Run: the deploy pipeline I ended up with</title>
      <dc:creator>Drew Fisher</dc:creator>
      <pubDate>Thu, 29 Oct 2026 01:20:48 +0000</pubDate>
      <link>https://dev.to/wired_fisher/moving-a-side-project-to-cloud-run-the-deploy-pipeline-i-ended-up-with-3b0g</link>
      <guid>https://dev.to/wired_fisher/moving-a-side-project-to-cloud-run-the-deploy-pipeline-i-ended-up-with-3b0g</guid>
      <description>&lt;p&gt;I moved a small side project from a single VM to Cloud Run mostly because I was tired of patching the box. This is the deploy pipeline I settled on, not the one I started with.&lt;/p&gt;

&lt;h2&gt;
  
  
  The first version was too clever
&lt;/h2&gt;

&lt;p&gt;My initial pipeline built the image, pushed it, deployed, and then ran a smoke test. It broke constantly: the smoke test ran before the new revision had any traffic, the rollback was "redeploy the previous image" typed by hand, and I once deployed on a Friday because I wasn't paying attention.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I have now
&lt;/h2&gt;

&lt;p&gt;A GitHub Actions workflow with three steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Build and push the image, tagged with the commit SHA. No &lt;code&gt;latest&lt;/code&gt;, ever. If I can't tell exactly what's running, I can't roll back.&lt;/li&gt;
&lt;li&gt;Deploy with &lt;code&gt;--no-traffic&lt;/code&gt;, which creates a revision without sending it live.&lt;/li&gt;
&lt;li&gt;Run the smoke test against the tagged revision URL, then move traffic with a single command.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The important part is step 2. Deploying a revision without traffic means a broken build never serves a single request, and the rollback is just "point traffic back at the previous revision" — one command, no rebuild.&lt;/p&gt;

&lt;h2&gt;
  
  
  Things that bit me
&lt;/h2&gt;

&lt;p&gt;Cloud Run sets &lt;code&gt;PORT&lt;/code&gt; for you. My app had a hardcoded 8080 and worked locally, then failed in production because the platform expected it to read the env var. Now I read &lt;code&gt;process.env.PORT&lt;/code&gt; first, with a local default.&lt;/p&gt;

&lt;p&gt;Health checks: I used to rely on the TCP check and it was useless. A real HTTP endpoint that checks the dependencies gives you a revision that fails to go healthy, which is far better than one that serves 500s.&lt;/p&gt;

&lt;p&gt;Secrets: never in the image. The runtime service account pulls them from Secret Manager at boot, or they're injected as env vars at deploy. I had one accidental commit of a &lt;code&gt;.env&lt;/code&gt; file early on and it scared me straight.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do with more traffic
&lt;/h2&gt;

&lt;p&gt;Traffic splitting by percentage, and maybe a canary step between smoke test and full rollout. For a side project that nobody is paying for, the current version is enough: broken revisions don't get traffic, rollback is one command, and I can deploy from a phone if I have to.&lt;/p&gt;

</description>
      <category>cloud</category>
      <category>devops</category>
      <category>github</category>
    </item>
    <item>
      <title>HTMX in an internal admin: less JS than expected</title>
      <dc:creator>Drew Fisher</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:50:21 +0000</pubDate>
      <link>https://dev.to/wired_fisher/htmx-in-an-internal-admin-less-js-than-expected-37f7</link>
      <guid>https://dev.to/wired_fisher/htmx-in-an-internal-admin-less-js-than-expected-37f7</guid>
      <description>&lt;p&gt;We needed an internal admin for a small service. The previous one was a React SPA that nobody wanted to maintain.&lt;/p&gt;

&lt;p&gt;This time we tried server-rendered HTML with HTMX. The result: about 40 lines of JavaScript in the whole app.&lt;/p&gt;

&lt;p&gt;What worked well:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Forms and tables are just HTML&lt;/li&gt;
&lt;li&gt;Partial updates via &lt;code&gt;hx-get&lt;/code&gt; / &lt;code&gt;hx-post&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;No build step for the admin&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What I missed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Client-side validation is clunkier&lt;/li&gt;
&lt;li&gt;Complex interactions (drag-and-drop) still need JS&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For an internal tool used by five people, it's the right trade. I'd still reach for a SPA for a consumer product.&lt;/p&gt;

&lt;p&gt;I'm learning HTMX properly now, and it's refreshing how much of the web you can get back.&lt;/p&gt;

</description>
      <category>htmx</category>
      <category>devops</category>
      <category>web</category>
    </item>
  </channel>
</rss>
