<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Clarence | Backend, AI, DevOps, Infrastructure</title>
    <link>https://clarence.tw/en/posts/</link>
    <description>Recent content in Posts on Clarence | Backend, AI, DevOps, Infrastructure</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 08 Jul 2026 00:30:00 +0800</lastBuildDate><atom:link href="https://clarence.tw/en/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I Work: Backend, AI, DevOps, and Infrastructure</title>
      <link>https://clarence.tw/en/posts/technical-delivery-chain/</link>
      <pubDate>Wed, 08 Jul 2026 00:30:00 +0800</pubDate>
      
      <guid>https://clarence.tw/en/posts/technical-delivery-chain/</guid>
      <description>&lt;p&gt;I do not treat Backend, AI, DevOps, Infrastructure, and Network as isolated areas. For a product that has to go online, be used, and remain maintainable, these layers eventually become one delivery chain.&lt;/p&gt;
&lt;p&gt;Features need stable APIs. Services need reliable CI/CD. Long-running systems need monitoring, backup, network visibility, and security. When a product needs LLMs, Speech AI, or GPU runtime, model integration also has to be deployable, observable, and operable.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>GitLab CI/CD Configuration Guide</title>
      <link>https://clarence.tw/en/posts/gitlab-cicd-complete-guide/</link>
      <pubDate>Tue, 30 Jan 2024 15:00:00 +0800</pubDate>
      
      <guid>https://clarence.tw/en/posts/gitlab-cicd-complete-guide/</guid>
      <description>&lt;p&gt;In enterprise DevOps work, I build and maintain GitLab CI/CD workflows from code submission to production deployment. This article summarizes the practical configuration patterns I use most often.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Reviewed July 11, 2026:&lt;/strong&gt; The examples now use GitLab Runner authentication tokens, Node.js 24 LTS, and Docker 29.6.1. Version and security defaults continue to change; check the current &lt;a href=&#34;https://docs.gitlab.com/runner/register/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;GitLab Runner registration documentation&lt;/a&gt;, &lt;a href=&#34;https://nodejs.org/en/about/previous-releases&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Node.js release status&lt;/a&gt;, and &lt;a href=&#34;https://docs.docker.com/engine/release-notes/29/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Docker Engine release notes&lt;/a&gt; before production use, then pin images to a version or digest your team has tested.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>High-traffic Web Hosting Operations</title>
      <link>https://clarence.tw/en/posts/hosting-high-bandwidth-web-server/</link>
      <pubDate>Sat, 21 Jan 2023 02:00:00 +0800</pubDate>
      
      <guid>https://clarence.tw/en/posts/hosting-high-bandwidth-web-server/</guid>
      <description>&lt;p&gt;I have operated a high-traffic hosting environment that hosted more than 4,000 websites. This kind of work is not just about running a web server. It requires capacity planning, monitoring, updates, security, DNS / CDN operations, incident response, and day-to-day maintenance discipline.&lt;/p&gt;
&lt;p&gt;At this scale, standardization matters. Every update, certificate change, configuration adjustment, and alert cannot depend only on human memory.&lt;/p&gt;
&lt;h3 id=&#34;cloudflare-30-day-metrics&#34;&gt;Cloudflare 30-day Metrics&lt;/h3&gt;
&lt;p&gt;The following chart shows one month of traffic:&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
