<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #serverless</title>
    <link>/tags/serverless/</link>
    <description>Recent bookmarks tagged #serverless</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:51 +0000</lastBuildDate>
    <item>
      <title>How I Track My Blog’s Analytics with Val Town</title>
      <link>https://orjpap.github.io/valtown/http/analytics/blog/jekyll/2025/04/15/blog-analytics.html</link>
      <description>Random morning thoughts: how many people actually visit this blog? Where do they come from? What if I could just spend a little time to build my own analytics?&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #analytics #data #serverless #sqlite #valtown #webdev&lt;/p&gt;</description>
      <pubDate>Mon, 21 Apr 2025 20:39:15 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:29567</guid>
      <category>analytics</category>
      <category>data</category>
      <category>serverless</category>
      <category>sqlite</category>
      <category>valtown</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Wasm is the new CGI | Roborooter.com</title>
      <link>https://roborooter.com/post/wasm-is-the-new-cgi/</link>
      <description>And to be clear I don&#39;t mean the Common Gateway Interface as a protocol. I mean what CGI and the cgi-bin application model brought to the web. They allowed people to easily write code that makes websites interactive. This shifted the web from an archive of documents to a vast network of applications. It was the first &#34;web application model&#34;. I think Wasm (WebAssembly) is setup to bring the next &#34;web application model&#34; to the industry.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #serverless #wasm #web #webdev&lt;/p&gt;</description>
      <pubDate>Thu, 10 Oct 2024 06:16:20 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:30440</guid>
      <category>serverless</category>
      <category>wasm</category>
      <category>web</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Compute@Edge: porting the iconic video game DOOM | Fastly</title>
      <link>https://www.fastly.com/blog/compute-edge-porting-the-iconic-video-game-doom</link>
      <description>Due to its approachable codebase and clean abstractions, id Software’s DOOM has become one of the most ported games in history. It felt like a perfect project to port to Compute@Edge, built on our serverless compute environment, to experiment with different applications of the product.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #doom #imported:pinboard #serverless&lt;/p&gt;</description>
      <pubDate>Sun, 25 Apr 2021 04:55:26 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:28963</guid>
      <category>doom</category>
      <category>imported:pinboard</category>
      <category>serverless</category>
    </item>
    <item>
      <title>How to set up a custom domain name for Lambda &amp; API Gateway with Serverless</title>
      <link>https://serverless.com/blog/serverless-api-gateway-domain/</link>
      <description>With Serverless, it&#39;s easier than ever to deploy production-ready API endpoints. However, using AWS API Gateway results in odd hostnames for your endpoints. Further, these hostnames will change if you remove and redeploy your service, which can cause problems for existing clients.&#xD;&#xA;&#xD;&#xA;In this guide, I&#39;ll show you how to map a custom domain name to your endpoints.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #aws #dns #imported:pinboard #serverless&lt;/p&gt;</description>
      <pubDate>Sat, 28 Apr 2018 20:32:35 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:31293</guid>
      <category>aws</category>
      <category>dns</category>
      <category>imported:pinboard</category>
      <category>serverless</category>
    </item>
    <item>
      <title>How to set up a custom domain name for Lambda &amp; API Gateway with Serverless</title>
      <link>https://serverless.com/blog/serverless-api-gateway-domain</link>
      <description>With Serverless, it&#39;s easier than ever to deploy production-ready API endpoints. However, using AWS API Gateway results in odd hostnames for your endpoints. Further, these hostnames will change if you remove and redeploy your service, which can cause problems for existing clients.&#xD;&#xA;&#xD;&#xA;In this guide, I&#39;ll show you how to map a custom domain name to your endpoints.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #aws #dns #serverless&lt;/p&gt;</description>
      <pubDate>Sat, 28 Apr 2018 20:32:35 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:27694</guid>
      <category>aws</category>
      <category>dns</category>
      <category>serverless</category>
    </item>
    <item>
      <title>Static Websites On AWS S3 With Serverless Framework</title>
      <link>https://www.serverlessops.io/blog/static-websites-on-aws-s3-with-serverless-framework</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #aws #imported:pinboard #s3 #serverless #static&lt;/p&gt;</description>
      <pubDate>Sat, 28 Apr 2018 20:30:01 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:27693</guid>
      <category>aws</category>
      <category>imported:pinboard</category>
      <category>s3</category>
      <category>serverless</category>
      <category>static</category>
    </item>
  </channel>
</rss>
