Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.peterbe.com/rss.xml

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Peterbe.com</title><link>http://www.peterbe.com/rss.xml</link><description>Stuff in Peter's head</description><atom:link href="http://www.peterbe.com/rss.xml" rel="self"/><language>en-us</language><lastBuildDate>Mon, 03 Nov 2025 16:40:49 +0000</lastBuildDate><item><title>Hosting your static web site with Firebase Hosting</title><link>http://www.peterbe.com/plog/hosting-your-static-web-site-with-firebase-hosting</link><description>&lt;p&gt;&lt;a href="https://firebase.google.com/docs/hosting"&gt;Firebase Hosting&lt;/a&gt; is a part of &lt;a href="https://firebase.google.com/"&gt;Firebase platform&lt;/a&gt;, the integrated real-time database, cloud functions, app auth, etc. But you can use just the Hosting feature.&lt;/p&gt;
  3. &lt;p&gt;Suppose you have a single-page app that builds a complete site with &lt;code&gt;index.html&lt;/code&gt; and &lt;code&gt;index-63gsxn38.css&lt;/code&gt; etc. All the files you need for static hosting. There are many options for hosting and exposing these via CDN such as Netlify, AWS S3 + CloudFront, Vercel, or your own Nginx server. But this guide is focussing on Firebase Hosting.&lt;/p&gt;
  4. &lt;p&gt;In my case, I can run &lt;code&gt;bun run build&lt;/code&gt; and then the &lt;code&gt;./dist/&lt;/code&gt; directory has everything. It has a &lt;code&gt;/index.html&lt;/code&gt;, some &lt;code&gt;.css&lt;/code&gt;, some &lt;code&gt;.js&lt;/code&gt;, some &lt;code&gt;favicon.svg&lt;/code&gt;, etc.&lt;/p&gt;
  5. &lt;p&gt;You can create the project in the &lt;a href="https://console.firebase.google.com/"&gt;Firebase Console&lt;/a&gt;, first, but you can leave that to the CLI. To get started, position yourself in the projects &lt;code&gt;git&lt;/code&gt; repository root. Not inside the &lt;code&gt;./dist/&lt;/code&gt; directory. It's going to ask you about adding GitHub workflow files, which I'm going to accept.&lt;/p&gt;
  6. &lt;pre&gt;bunx firebase --version
  7. bunx firebase init hosting&lt;/pre&gt;
  8.  
  9. &lt;p&gt;It will ask serveral questions. In my case, it picked a default name for the project ID (and project name) to be that of the directory that the git repository root is in. So if you did &lt;code&gt;cd ~/myprojects/that-webapp &amp;amp;&amp;amp; bunx firebase init hosting&lt;/code&gt; it's going to suggest to call the project &lt;code&gt;that-webapp&lt;/code&gt; for the project ID.&lt;/p&gt;
  10. &lt;p&gt;Next question is going to be the name of the project. It defaults to be the same as the project ID. But this is where you might, for example, call it "That WebApp". Unlike the project ID, this name does not have to be globally unique.&lt;/p&gt;
  11. &lt;p&gt;In my example, I get this lovely output:&lt;/p&gt;
  12. &lt;p&gt;&lt;a href="/cache/03/04/03041e25d47cc7463c00714a94091603.png"&gt;&lt;img src="/cache/03/04/03041e25d47cc7463c00714a94091603.png" class="fullsize" style="width:70%"&gt;&lt;/a&gt;&lt;/p&gt;
  13. &lt;p&gt;The next step is specifically for Hosting. It'll ask you some details such as what is the "public directory". In my case, I had to replace the default suggestion (&lt;code&gt;public/&lt;/code&gt;) for what my output directory is called; &lt;code&gt;dist/&lt;/code&gt;.&lt;/p&gt;
  14. &lt;p&gt;Next, it's going to ask you about setting up the relevant files for GitHub Workflows to auto-deploy. You can say yes to all the GitHub deployment related questions, and tune the code it generates, later.&lt;/p&gt;
  15. &lt;p&gt;When it's done, it'll have generated these files:&lt;/p&gt;
  16. &lt;ul&gt;
  17. &lt;li&gt;&lt;code&gt;.firebaserc&lt;/code&gt;: information about the Firebase project&lt;/li&gt;
  18. &lt;li&gt;&lt;code&gt;firebase.json&lt;/code&gt;: configuration for the hosting&lt;/li&gt;
  19. &lt;li&gt;&lt;code&gt;.github/workflows/firebase-hosting-pull-request.yml&lt;/code&gt;: so each PR gets its own temporary site&lt;/li&gt;
  20. &lt;li&gt;&lt;code&gt;.github/workflows/firebase-hosting-merge.yml&lt;/code&gt;: for pushing the deployed site into production when you merge pull requests&lt;/li&gt;
  21. &lt;/ul&gt;
  22. &lt;p&gt;Now, create a PR with all these new files. &lt;a href="https://github.com/peterbe/hylite-demo/pull/4"&gt;Here's one such example PR&lt;/a&gt;.&lt;/p&gt;
  23. &lt;p&gt;What you should be aware of, with the CLI, it will authenticate to your GitHub account so that it can go in to your repository settings and &lt;em&gt;add&lt;/em&gt; the necessary credentials as repo secrets.&lt;/p&gt;
  24. &lt;p&gt;Note, it's likely not going to work at first. In my case, the initialization CLI asked for the instructions for building the site. But what's missing from the GitHub Action workflow, is how do you get the runtime. I had to make this change manually:&lt;/p&gt;
  25. &lt;pre&gt;&lt;code class="hljs"&gt;
  26. &lt;span class="hljs-comment"&gt;diff --git a/.github/workflows/firebase-hosting-pull-request.yml b/.github/workflows/firebase-hosting-pull-request.yml&lt;/span&gt;
  27. &lt;span class="hljs-comment"&gt;index 8cd1813..0479a03 100644&lt;/span&gt;
  28. &lt;span class="hljs-comment"&gt;--- a/.github/workflows/firebase-hosting-pull-request.yml&lt;/span&gt;
  29. &lt;span class="hljs-comment"&gt;+++ b/.github/workflows/firebase-hosting-pull-request.yml&lt;/span&gt;
  30. &lt;span class="hljs-meta"&gt;@@ -12,7 +12,9 @@&lt;/span&gt; jobs:
  31.     if: ${{ github.event.pull_request.head.repo.full_name == github.repository }}
  32.     runs-on: ubuntu-latest
  33.     steps:
  34. &lt;span class="hljs-deletion"&gt;-      - uses: actions/checkout@v4&lt;/span&gt;
  35. &lt;span class="hljs-addition"&gt;+      - uses: actions/checkout@v5&lt;/span&gt;
  36. &lt;span class="hljs-addition"&gt;+      - uses: oven-sh/setup-bun@v2&lt;/span&gt;
  37. &lt;span class="hljs-addition"&gt;+      - run: bun install&lt;/span&gt;
  38.       - run: bun run build
  39.       - uses: FirebaseExtended/action-hosting-deploy@v0
  40.         with:
  41. &lt;/code&gt;&lt;/pre&gt;
  42.  
  43. &lt;p&gt;Once your "Deploy to Firebase Hosting on PR" workflow works and passes, you'll see a comment on the PR, like this:&lt;/p&gt;
  44. &lt;!--&lt;a href="/cache/21/c3/21c3282558d1d0ca691ab7c477df22ab.png"&gt;&lt;img src="/cache/a9/5c/a95c1500cad896d1003722025a02abaf.png" alt="PR comment" width="370" height="164"&gt;&lt;/a&gt;--&gt;
  45.  
  46. &lt;p&gt;&lt;a href="/cache/21/c3/21c3282558d1d0ca691ab7c477df22ab.png"&gt;&lt;img src="/cache/21/c3/21c3282558d1d0ca691ab7c477df22ab.png" alt="PR comment" class="fullsize" style="width:70%" /&gt;&lt;/a&gt;&lt;/p&gt;
  47. &lt;h3 id="domain-name"&gt;&lt;a class="toclink" href="#domain-name"&gt;Domain name&lt;/a&gt;&lt;/h3&gt;
  48. &lt;p&gt;By default, it will deploy your site to a domain that is &lt;code&gt;https://your-project-id.web.app/&lt;/code&gt;. &lt;a href="https://hylite-demo.web.app/"&gt;https://hylite-demo.web.app/ for example&lt;/a&gt;.&lt;/p&gt;
  49. &lt;p&gt;Suppose you want your own domain there instead of &lt;code&gt;web.app&lt;/code&gt;. You can accomplish this by adding a &lt;code&gt;CNAME&lt;/code&gt; for your domain name. To get started, start within the Hosting portion of the Firebase project's Build settings. Find Hosting, and look for this button:&lt;/p&gt;
  50. &lt;p&gt;&lt;a href="/cache/01/31/0131872164378564eeeb6149a863608c.png"&gt;&lt;img src="/cache/01/31/0131872164378564eeeb6149a863608c.png" class="fullsize" style="width:60%"&gt;&lt;/a&gt;&lt;/p&gt;
  51. &lt;p&gt;Follow the steps and when you get the last modal, copy that into your DNS provider.  After you've done that, come back to the Firebase hosting setup and press "Verify"&lt;/p&gt;
  52. &lt;p&gt;That's it. All you have to do now is wait for a cert to be generated and propagate to DNS.&lt;/p&gt;
  53. &lt;p&gt;In my example, when all is done I have a custom domain name pointing to a kick-butt CDN that is as easy to deploy to as merging a PR: &lt;a href="https://hylite-demo.peterbe.com/"&gt;https://hylite-demo.peterbe.com/&lt;/a&gt;&lt;/p&gt;
  54. &lt;h3 id="optimizations"&gt;&lt;a class="toclink" href="#optimizations"&gt;Optimizations&lt;/a&gt;&lt;/h3&gt;
  55. &lt;p&gt;One thing I often like to do is to inform Firebase Hosting, which URLs can be cached aggressively. Here's a great example of an addition to the &lt;code&gt;firebase.json&lt;/code&gt; file:&lt;/p&gt;
  56. &lt;pre&gt;&lt;code class="hljs"&gt;
  57. &lt;span class="hljs-comment"&gt;diff --git a/firebase.json b/firebase.json&lt;/span&gt;
  58. &lt;span class="hljs-comment"&gt;index 6564edd..533e3e6 100644&lt;/span&gt;
  59. &lt;span class="hljs-comment"&gt;--- a/firebase.json&lt;/span&gt;
  60. &lt;span class="hljs-comment"&gt;+++ b/firebase.json&lt;/span&gt;
  61. &lt;span class="hljs-meta"&gt;@@ -7,6 +7,17 @@&lt;/span&gt;
  62.         &amp;quot;source&amp;quot;: &amp;quot;**&amp;quot;,
  63.         &amp;quot;destination&amp;quot;: &amp;quot;/index.html&amp;quot;
  64.       }
  65. &lt;span class="hljs-addition"&gt;+    ],&lt;/span&gt;
  66. &lt;span class="hljs-addition"&gt;+    &amp;quot;headers&amp;quot;: [&lt;/span&gt;
  67. &lt;span class="hljs-addition"&gt;+      {&lt;/span&gt;
  68. &lt;span class="hljs-addition"&gt;+        &amp;quot;source&amp;quot;: &amp;quot;/assets/**/*.*&amp;quot;,&lt;/span&gt;
  69. &lt;span class="hljs-addition"&gt;+        &amp;quot;headers&amp;quot;: [&lt;/span&gt;
  70. &lt;span class="hljs-addition"&gt;+          {&lt;/span&gt;
  71. &lt;span class="hljs-addition"&gt;+            &amp;quot;key&amp;quot;: &amp;quot;Cache-Control&amp;quot;,&lt;/span&gt;
  72. &lt;span class="hljs-addition"&gt;+            &amp;quot;value&amp;quot;: &amp;quot;public,max-age=315360000&amp;quot;&lt;/span&gt;
  73. &lt;span class="hljs-addition"&gt;+          }&lt;/span&gt;
  74. &lt;span class="hljs-addition"&gt;+        ]&lt;/span&gt;
  75. &lt;span class="hljs-addition"&gt;+      }&lt;/span&gt;
  76.     ]
  77.   }
  78. }
  79. &lt;/code&gt;&lt;/pre&gt;
  80.  
  81. &lt;p&gt;I think it's self explanatory what it does. It can be a smidge tricky to get all of these right but thankfully &lt;a href="https://firebase.google.com/docs/hosting/full-config#headers"&gt;the documentation is great&lt;/a&gt;.&lt;/p&gt;</description><pubDate>Mon, 03 Nov 2025 16:40:49 +0000</pubDate><guid>http://www.peterbe.com/plog/hosting-your-static-web-site-with-firebase-hosting</guid></item><item><title>Bun vs. Go for a basic web server benchmark</title><link>http://www.peterbe.com/plog/bun-go-basic-web-server-benchmark</link><description>&lt;p&gt;&lt;strong&gt;tl;dr; Bun is plenty fast to serve as a basic web server that does no I/O. It's even faster than Go using &lt;code&gt;fasthttp&lt;/code&gt;.&lt;/strong&gt;&lt;/p&gt;
  82. &lt;p&gt;Doing a "Hello World" benchmark comparison is rather contrived because it's so unrealistic. No server does no I/O. However, it's good to know that if you do need something as simple as this, and need raw performance, you don't need as statically compiled language like Go. Bun is fast enough.&lt;/p&gt;
  83. &lt;p&gt;Inspired by &lt;a href="https://medium.com/deno-the-complete-reference/bun-v-s-go-hello-world-performance-comparison-1f5418945112"&gt;this blog post&lt;/a&gt; from 2023, I wanted to retry it using Bun 1.3 that &lt;a href="https://bun.com/blog/bun-v1.3"&gt;came out the other day&lt;/a&gt;. Honestly, I was nerdily curious how it would fly on my M4 MacBook Pro.&lt;/p&gt;
  84. &lt;p&gt;Check out the code on: &lt;a href="https://github.com/peterbe/go-bun-compare"&gt;https://github.com/peterbe/go-bun-compare&lt;/a&gt;&lt;/p&gt;
  85. &lt;p&gt;&lt;strong&gt;Gist: Bun is slightly faster than Go.&lt;/strong&gt; &lt;a href="https://github.com/peterbe/go-bun-compare?tab=readme-ov-file#my-current-results"&gt;By about 15%&lt;/a&gt;.&lt;/p&gt;
  86. &lt;p&gt;Take it with a pinch of salt. These kinds of benchmarks have flaws because the unrealistic scenario, the lack of logging, and lack of other features such as middleware.&lt;/p&gt;
  87. &lt;h4 id="bonuses"&gt;&lt;a class="toclink" href="#bonuses"&gt;Bonuses&lt;/a&gt;&lt;/h4&gt;
  88. &lt;p&gt;The &lt;a href="https://github.com/peterbe/go-bun-compare/blob/main/README.md"&gt;README&lt;/a&gt; has a couple of interesting bonuses such as throwing in Python into the mix.&lt;/p&gt;
  89. &lt;p&gt;One that peaked my interest was; how does running a compiled executable, from Bun, compare to running it directly with &lt;code&gt;bun run ...&lt;/code&gt;. I ran it a bunch of times and noticed that executing it as a single binary made it &lt;strong&gt;about 3% faster&lt;/strong&gt;. Curious!&lt;/p&gt;</description><pubDate>Fri, 24 Oct 2025 01:23:26 +0000</pubDate><guid>http://www.peterbe.com/plog/bun-go-basic-web-server-benchmark</guid></item><item><title>hylite as an executable</title><link>http://www.peterbe.com/plog/hylite-as-an-executable</link><description>github.com/peterbe/hylite is now available as downloadable single-file executables</description><pubDate>Wed, 15 Oct 2025 23:23:33 +0000</pubDate><guid>http://www.peterbe.com/plog/hylite-as-an-executable</guid></item><item><title>In Python, you have to specify the type and not rely on inference</title><link>http://www.peterbe.com/plog/in-python-you-have-to-specify-the-type-and-not-rely-on-inference</link><description>Unlike TypeScript, if you give a variable a default, which has a type, that variable is implied to always have the type of the default. That's not the case with mypy and ty.</description><pubDate>Fri, 10 Oct 2025 13:07:37 +0000</pubDate><guid>http://www.peterbe.com/plog/in-python-you-have-to-specify-the-type-and-not-rely-on-inference</guid></item><item><title>Find the source of an alias in bash</title><link>http://www.peterbe.com/plog/find-the-source-of-an-alias-in-bash</link><description>&lt;p&gt;This is borderline embarrassing but by blogging about it, at least there's hope that &lt;em&gt;I&lt;/em&gt; will not forget this.&lt;/p&gt;
  90. &lt;p&gt;If you have an executable, you can type &lt;code&gt;which&lt;/code&gt; to find out its full path. For example:&lt;/p&gt;
  91. &lt;pre&gt;&lt;code class="hljs"&gt;
  92. $ which fdfind
  93. /usr/bin/fdfind
  94. &lt;/code&gt;&lt;/pre&gt;
  95.  
  96. &lt;p&gt;then you can do something with that. But if the executable is an alias? E.g. I have set up &lt;code&gt;alias fd='fdfind'&lt;/code&gt; and suppose I don't remember that. I have this executable, &lt;code&gt;gbranch&lt;/code&gt;, but you can't use &lt;code&gt;which&lt;/code&gt; on it:&lt;/p&gt;
  97. &lt;pre&gt;&lt;code class="hljs"&gt;
  98. $ which fd
  99. &lt;/code&gt;&lt;/pre&gt;
  100.  
  101. &lt;p&gt;It outputs nothing and you get an exit code of 1.&lt;/p&gt;
  102. &lt;p&gt;Lo and behold, it's so basic, run the &lt;code&gt;alias&lt;/code&gt; command on it:&lt;/p&gt;
  103. &lt;pre&gt;&lt;code class="hljs"&gt;
  104. $ alias fd
  105. alias fd=&amp;#x27;fdfind&amp;#x27;
  106. &lt;/code&gt;&lt;/pre&gt;</description><pubDate>Mon, 29 Sep 2025 19:04:01 +0000</pubDate><guid>http://www.peterbe.com/plog/find-the-source-of-an-alias-in-bash</guid></item><item><title>From @monaco-editor/react to prism-react-editor</title><link>http://www.peterbe.com/plog/from-monaco-to-prism-react-editor</link><description>Switching from @monaco-editor/react to prism-react-editor means a less powerful in-browser editor but it's much lighter.</description><pubDate>Thu, 25 Sep 2025 21:18:29 +0000</pubDate><guid>http://www.peterbe.com/plog/from-monaco-to-prism-react-editor</guid></item><item><title>How I end-to-end test my Bun CLI app</title><link>http://www.peterbe.com/plog/how-i-end-to-end-test-my-bun-cli-app</link><description>Bun $ Shell makes it easy to write end-to-end tests that tests command line scripts.</description><pubDate>Thu, 18 Sep 2025 18:48:16 +0000</pubDate><guid>http://www.peterbe.com/plog/how-i-end-to-end-test-my-bun-cli-app</guid></item><item><title>How to count the number of non-blank lines with Bash</title><link>http://www.peterbe.com/plog/how-to-count-the-number-of-non-blank-lines-with-bash</link><description>You can use `awk 'NF &gt; 0'` to filter blank lines before piping to `wc` to filter out blank lines.</description><pubDate>Wed, 03 Sep 2025 15:08:07 +0000</pubDate><guid>http://www.peterbe.com/plog/how-to-count-the-number-of-non-blank-lines-with-bash</guid></item><item><title>gg commit with suggested --no-verify</title><link>http://www.peterbe.com/plog/gg-commit-with-suggested-no-verify</link><description>&lt;p&gt;In version &lt;a href="https://github.com/peterbe/gg2/releases/tag/v0.0.11"&gt;0.0.11&lt;/a&gt; of &lt;a href="https://github.com/peterbe/gg2"&gt;gg&lt;/a&gt; you can now type &lt;code&gt;gg commit Bla bla&lt;/code&gt; and it will try to commit but if that fails, it will ask you one more time, if you want to re-attempt to commit but with &lt;code&gt;--no-verify&lt;/code&gt;.&lt;/p&gt;
  107. &lt;p&gt;For example:&lt;/p&gt;
  108. &lt;pre&gt;&lt;code class="hljs"&gt;
  109. $ gg commit This is my commit message
  110. ❌ file has formatting problems
  111. Commit failed and you did not use --no-verify.
  112. ? Try again but with --no-verify? (y/N)
  113. &lt;/code&gt;&lt;/pre&gt;
  114.  
  115. &lt;p&gt;(&lt;em&gt;see screenshots below where color makes these things more intuitive&lt;/em&gt;)&lt;/p&gt;
  116. &lt;p&gt;This is handy when you know that the &lt;code&gt;.git/hooks/pre-commit&lt;/code&gt; might be failing for a reason that is actually not a problem &lt;em&gt;after&lt;/em&gt; you've committed.&lt;/p&gt;
  117. &lt;p&gt;In a sample repo I have:&lt;/p&gt;
  118. &lt;pre&gt;&lt;code class="hljs"&gt;
  119. $ &lt;span class="hljs-built_in"&gt;cat&lt;/span&gt; .git/hooks/pre-commit
  120. &lt;span class="hljs-comment"&gt;#!/bin/sh&lt;/span&gt;
  121.  
  122. &lt;span class="hljs-built_in"&gt;echo&lt;/span&gt; &lt;span class="hljs-string"&gt;&amp;quot;❌ Rejecting all commits like an angry troll&amp;quot;&lt;/span&gt;
  123. &lt;span class="hljs-built_in"&gt;exit&lt;/span&gt; 1
  124. &lt;/code&gt;&lt;/pre&gt;
  125.  
  126. &lt;p&gt;And when I use &lt;code&gt;gg commit ...&lt;/code&gt; this happens:&lt;/p&gt;
  127. &lt;p&gt;&lt;a href="/cache/5a/45/5a45eeb1b7d7baebdc9d07e6eb652fc8.png"&gt;&lt;img src="/cache/ff/ff/ffff529524b78fb3a84267679f8519ee.png" alt="Prompt"  width="370" height="90"&gt;&lt;/a&gt;&lt;/p&gt;
  128. &lt;p&gt;&lt;a href="/cache/67/10/671041199ffb99018237b945e483c761.png"&gt;&lt;img src="/cache/87/0e/870e49b633d6cddde804121623bd08e1.png" alt="Said y for Yes"  width="370" height="147"&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Fri, 29 Aug 2025 18:37:45 +0000</pubDate><guid>http://www.peterbe.com/plog/gg-commit-with-suggested-no-verify</guid></item><item><title>Faster way to sum an integer series in Python</title><link>http://www.peterbe.com/plog/faster-way-to-sum-an-integer-series-in-python</link><description>You can sum a simple series with `n(n+1)/2`</description><pubDate>Thu, 28 Aug 2025 12:11:22 +0000</pubDate><guid>http://www.peterbe.com/plog/faster-way-to-sum-an-integer-series-in-python</guid></item></channel></rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.peterbe.com/rss.xml

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda