<?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: 薛定谔的快乐</title>
    <description>The latest articles on DEV Community by 薛定谔的快乐 (@9904099).</description>
    <link>https://dev.to/9904099</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%2F4185748%2Fa38392dd-3a83-4467-883f-b3e507b545e8.png</url>
      <title>DEV Community: 薛定谔的快乐</title>
      <link>https://dev.to/9904099</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/9904099"/>
    <language>en</language>
    <item>
      <title>Project NOMAD Storage Moves: Keep These Three Paths Identical</title>
      <dc:creator>薛定谔的快乐</dc:creator>
      <pubDate>Tue, 10 Nov 2026 01:15:53 +0000</pubDate>
      <link>https://dev.to/9904099/project-nomad-storage-moves-keep-these-three-paths-identical-3hnk</link>
      <guid>https://dev.to/9904099/project-nomad-storage-moves-keep-these-three-paths-identical-3hnk</guid>
      <description>&lt;p&gt;This is a third-party deployment note, not official Project NOMAD or Crosstalk Solutions documentation. It focuses on manual Compose installation and a storage-migration pitfall that can make an existing content library appear empty.&lt;/p&gt;

&lt;p&gt;Project NOMAD is an offline-first knowledge and education server for material such as Wikipedia, books, courses, and maps. Installation and content downloads need connectivity; downloaded content can then remain available without public internet access.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the supported deployment shape
&lt;/h2&gt;

&lt;p&gt;The guide’s main path is an x86_64 Debian/Ubuntu host. An installation script is available, while an existing Docker host can use the supplied &lt;code&gt;management_compose.yaml&lt;/code&gt; template manually.&lt;/p&gt;

&lt;p&gt;For the manual route, keep &lt;code&gt;docker-compose.yml&lt;/code&gt; in &lt;code&gt;/opt/project-nomad&lt;/code&gt;. The updater mounts that directory to modify image references. Replace every &lt;code&gt;replaceme&lt;/code&gt; placeholder before startup:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Set &lt;code&gt;APP_KEY&lt;/code&gt; to at least 16 characters.&lt;/li&gt;
&lt;li&gt;Set &lt;code&gt;URL&lt;/code&gt; to the address the browser will actually use.&lt;/li&gt;
&lt;li&gt;Make &lt;code&gt;DB_PASSWORD&lt;/code&gt; and &lt;code&gt;MYSQL_PASSWORD&lt;/code&gt; identical.&lt;/li&gt;
&lt;li&gt;Give &lt;code&gt;MYSQL_ROOT_PASSWORD&lt;/code&gt; its own strong value.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;NOMAD has no authentication by default. Keep the management interface, log viewer, and application ports off the public internet. Several services mount the Docker socket, so access to the management interface carries significant control over the host’s containers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pitfall: changing only one storage reference
&lt;/h2&gt;

&lt;p&gt;The default content directory appears in three places. These are excerpts from separate parts of the Compose template, not one block to paste together:&lt;/p&gt;

&lt;p&gt;Admin service volume:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;/opt/project-nomad/storage:/app/storage&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Admin environment variable:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;NOMAD_STORAGE_PATH=/opt/project-nomad/storage&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Disk-collector volume:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;/opt/project-nomad/storage:/storage&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;All three host paths must match exactly, including letter case.&lt;/strong&gt; The container destinations differ intentionally; the host-side directory is what must stay consistent.&lt;/p&gt;

&lt;p&gt;For example, &lt;code&gt;/mnt/Data&lt;/code&gt; and &lt;code&gt;/mnt/data&lt;/code&gt; are different paths. A typo can cause Docker to create a new empty directory. The interface then shows an empty library, making content look as though it “disappeared” after the move. Pointing the deployment at an empty directory does not make it discover the previous files automatically.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix the move as a complete operation
&lt;/h2&gt;

&lt;p&gt;Follow the migration sequence rather than changing a mount while the stack is running:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Stop the stack with &lt;code&gt;docker compose down&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Move the original storage directory to its new location, preserving subdirectories such as &lt;code&gt;/zim&lt;/code&gt; and &lt;code&gt;/models&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Change the host side of the admin bind mount.&lt;/li&gt;
&lt;li&gt;Set &lt;code&gt;NOMAD_STORAGE_PATH&lt;/code&gt; to that exact same host path.&lt;/li&gt;
&lt;li&gt;Change the host side of the disk-collector mount to match.&lt;/li&gt;
&lt;li&gt;Start with &lt;code&gt;docker compose up -d&lt;/code&gt;, then check both content and disk usage in the interface.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the library is empty, stop again and compare all three references with the actual directory containing the original files. For external or network storage, mount it on the host first; NOMAD does not configure the storage protocol itself. MySQL and Redis have separate data directories, so the content-storage setting is not a replacement for those mounts.&lt;/p&gt;

&lt;h2&gt;
  
  
  A small port-mapping check
&lt;/h2&gt;

&lt;p&gt;If host port 8080 is occupied, change only the left side of the mapping and update &lt;code&gt;URL&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"9090:8080"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Leave the container’s &lt;code&gt;PORT=8080&lt;/code&gt; unchanged.&lt;/p&gt;

&lt;p&gt;Finally, Docker availability alone does not make every NAS a supported target. NAS graphical stack imports are outside the documented support path, and Raspberry Pi/ARM was not officially tested or supplied with official images at the guide’s check time.&lt;/p&gt;

&lt;p&gt;The full Chinese step-by-step guide (install script or manual Compose, NAS / Raspberry Pi boundaries, troubleshooting) is here: &lt;a href="https://9012938178391.gumroad.com/l/tjlxtb" rel="noopener noreferrer"&gt;https://9012938178391.gumroad.com/l/tjlxtb&lt;/a&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>selfhosted</category>
      <category>linux</category>
      <category>homelab</category>
    </item>
    <item>
      <title>CopilotKit OpenBot v1.0.0 on a VPS: Digest Pinning, Loopback Ports, and the Missing Routines Worker</title>
      <dc:creator>薛定谔的快乐</dc:creator>
      <pubDate>Tue, 10 Nov 2026 01:13:38 +0000</pubDate>
      <link>https://dev.to/9904099/copilotkit-openbot-v100-on-a-vps-digest-pinning-loopback-ports-and-the-missing-routines-worker-3hd</link>
      <guid>https://dev.to/9904099/copilotkit-openbot-v100-on-a-vps-digest-pinning-loopback-ports-and-the-missing-routines-worker-3hd</guid>
      <description>&lt;p&gt;This is a third-party deployment note, not official CopilotKit / OpenBot documentation. It covers one checked path for &lt;strong&gt;v1.0.0&lt;/strong&gt;: the official all-in-one image, a minimal Compose wrapper, and HTTPS on the host with Caddy. It is not the repository root development Compose, and it does not cover Helm or supervisor multi-tenant layouts.&lt;/p&gt;

&lt;p&gt;CopilotKit/OpenBot is also not OpenMausBot (local-first CLI engine orchestration with pairing login), and not nightly-labs/openbot (a separate product line and license).&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the public surface small
&lt;/h2&gt;

&lt;p&gt;Start with Docker Engine, Compose V2, and a hostname whose A record points at the VPS. Inbound website traffic should be TCP 80 and 443 only. Do not publish &lt;strong&gt;3001&lt;/strong&gt;, &lt;strong&gt;4100&lt;/strong&gt;, or &lt;strong&gt;5432&lt;/strong&gt; to the internet—check IPv6 and cloud security groups the same way you check IPv4.&lt;/p&gt;

&lt;p&gt;The application listens on port 3001 inside the container. Map that port to loopback only:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;ports&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"127.0.0.1:3001:3001"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Put a host Caddy site block in front of that listener:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;openbot.example.com {
    reverse_proxy 127.0.0.1:3001
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Replace the hostname with yours. Caddy handles certificates and forwarding; there is no need to expose 4100 as a separate public location. If Caddy runs in another container instead of on the host, &lt;code&gt;127.0.0.1&lt;/code&gt; refers to that other container—do not “fix” reachability by binding 3001 to a public address.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pin the release digest, not &lt;code&gt;latest&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;At the guide’s check time (&lt;strong&gt;2026-11-10&lt;/strong&gt;, Asia/Shanghai), v1.0.0 is commit &lt;code&gt;ac9c16f72bf2690d3bc968dddde3e160819f4e13&lt;/code&gt;. The release asset &lt;code&gt;container-images.json&lt;/code&gt; lists the all-in-one image as:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ghcr.io/copilotkit/openbot@sha256:ee4bb211c066a2f15c6260889173aeb148d769b7f52575d5bcf9cf001f53a60c
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Download that manifest, inspect the digest on the VPS (&lt;code&gt;docker buildx imagetools inspect&lt;/code&gt; or &lt;code&gt;docker manifest inspect&lt;/code&gt;), then pull and run that reference. Do not assume &lt;code&gt;latest&lt;/code&gt; matches the release you just read. A &lt;code&gt;no matching manifest&lt;/code&gt; error means the host architecture does not match the digest’s platforms—switch machines or build from the v1.0.0 source tree; do not swap to &lt;code&gt;latest&lt;/code&gt; to hide the mismatch.&lt;/p&gt;

&lt;p&gt;The Compose service should use that digest as &lt;code&gt;image&lt;/code&gt;, enable embedded PostgreSQL when you want the single-container path (&lt;code&gt;EMBEDDED_POSTGRES=on&lt;/code&gt;), and keep three named volumes for PostgreSQL data, the bot workspace directory, and browser profiles. After &lt;code&gt;up -d&lt;/code&gt;, check &lt;code&gt;http://127.0.0.1:3001/health&lt;/code&gt; locally, then &lt;code&gt;https://your-domain/health&lt;/code&gt; through Caddy.&lt;/p&gt;

&lt;h2&gt;
  
  
  The concrete pitfall: routines look scheduled, but nothing fires
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The all-in-one image does not include a scheduled routines worker, and it does not periodically cull unsent attachments.&lt;/strong&gt; Official deployment docs state this boundary clearly. The Routines UI can show a next run time even though nothing will trigger that run. The same image ships one-shot scripts such as &lt;code&gt;bun scripts/fire-routines.ts&lt;/code&gt; and &lt;code&gt;bun scripts/cull-staged-attachments.ts&lt;/code&gt; under &lt;code&gt;/app/server&lt;/code&gt;, but the single container does not run them on a timer for you.&lt;/p&gt;

&lt;p&gt;Without an external scheduler (and a verified worker / environment injection path), routines never fire on their own. Staged attachments that stay unsent can keep consuming quota—official deployment notes list a server-side cap of 32 unsent attachments per person, up to 8 MiB each—until uploads start failing.&lt;/p&gt;

&lt;p&gt;Do not treat a healthy single container as an unattended production install until those two jobs are scheduled and verified outside the all-in-one process. Restarting the web UI does not install a worker. If you start a second container from the same image to run a script, override the entrypoint so &lt;code&gt;/init&lt;/code&gt; does not bring up a second full service stack.&lt;/p&gt;

&lt;h2&gt;
  
  
  Login and what to preserve
&lt;/h2&gt;

&lt;p&gt;Public HTTPS alone is not authentication. Configure a real identity provider (Google, Microsoft, or Okta callbacks under &lt;code&gt;/api/auth/callback/...&lt;/code&gt;), set &lt;code&gt;INITIAL_ADMIN_EMAILS&lt;/code&gt;, and keep Intelligence and model credentials separate—both are required for a full start on this path. Before upgrades, cold-back up &lt;code&gt;.env&lt;/code&gt;, Compose, the release image list, and the three volumes; restore only onto matching digests and empty verification volumes.&lt;/p&gt;

&lt;p&gt;The full Chinese step-by-step guide (Compose + host Caddy HTTPS, login, backups, routine scheduling notes) is here: &lt;a href="https://9012938178391.gumroad.com/l/igtblm" rel="noopener noreferrer"&gt;https://9012938178391.gumroad.com/l/igtblm&lt;/a&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>selfhosted</category>
      <category>devops</category>
      <category>linux</category>
    </item>
    <item>
      <title>Project NOMAD Storage Moves: Keep These Three Paths Identical</title>
      <dc:creator>薛定谔的快乐</dc:creator>
      <pubDate>Mon, 09 Nov 2026 22:39:34 +0000</pubDate>
      <link>https://dev.to/9904099/project-nomad-storage-moves-keep-these-three-paths-identical-f7n</link>
      <guid>https://dev.to/9904099/project-nomad-storage-moves-keep-these-three-paths-identical-f7n</guid>
      <description>&lt;p&gt;This is a third-party deployment note, not official Project NOMAD or Crosstalk Solutions documentation. It focuses on manual Compose installation and a storage-migration pitfall that can make an existing content library appear empty.&lt;/p&gt;

&lt;p&gt;Project NOMAD is an offline-first knowledge and education server for material such as Wikipedia, books, courses, and maps. Installation and content downloads need connectivity; downloaded content can then remain available without public internet access.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the supported deployment shape
&lt;/h2&gt;

&lt;p&gt;The guide’s main path is an x86_64 Debian/Ubuntu host. An installation script is available, while an existing Docker host can use the supplied &lt;code&gt;management_compose.yaml&lt;/code&gt; template manually.&lt;/p&gt;

&lt;p&gt;For the manual route, keep &lt;code&gt;docker-compose.yml&lt;/code&gt; in &lt;code&gt;/opt/project-nomad&lt;/code&gt;. The updater mounts that directory to modify image references. Replace every &lt;code&gt;replaceme&lt;/code&gt; placeholder before startup:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Set &lt;code&gt;APP_KEY&lt;/code&gt; to at least 16 characters.&lt;/li&gt;
&lt;li&gt;Set &lt;code&gt;URL&lt;/code&gt; to the address the browser will actually use.&lt;/li&gt;
&lt;li&gt;Make &lt;code&gt;DB_PASSWORD&lt;/code&gt; and &lt;code&gt;MYSQL_PASSWORD&lt;/code&gt; identical.&lt;/li&gt;
&lt;li&gt;Give &lt;code&gt;MYSQL_ROOT_PASSWORD&lt;/code&gt; its own strong value.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;NOMAD has no authentication by default. Keep the management interface, log viewer, and application ports off the public internet. Several services mount the Docker socket, so access to the management interface carries significant control over the host’s containers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pitfall: changing only one storage reference
&lt;/h2&gt;

&lt;p&gt;The default content directory appears in three places. These are excerpts from separate parts of the Compose template, not one block to paste together:&lt;/p&gt;

&lt;p&gt;Admin service volume:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;/opt/project-nomad/storage:/app/storage&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Admin environment variable:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;NOMAD_STORAGE_PATH=/opt/project-nomad/storage&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Disk-collector volume:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;/opt/project-nomad/storage:/storage&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;All three host paths must match exactly, including letter case.&lt;/strong&gt; The container destinations differ intentionally; the host-side directory is what must stay consistent.&lt;/p&gt;

&lt;p&gt;For example, &lt;code&gt;/mnt/Data&lt;/code&gt; and &lt;code&gt;/mnt/data&lt;/code&gt; are different paths. A typo can cause Docker to create a new empty directory. The interface then shows an empty library, making content look as though it “disappeared” after the move. Pointing the deployment at an empty directory does not make it discover the previous files automatically.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix the move as a complete operation
&lt;/h2&gt;

&lt;p&gt;Follow the migration sequence rather than changing a mount while the stack is running:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Stop the stack with &lt;code&gt;docker compose down&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Move the original storage directory to its new location, preserving subdirectories such as &lt;code&gt;/zim&lt;/code&gt; and &lt;code&gt;/models&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Change the host side of the admin bind mount.&lt;/li&gt;
&lt;li&gt;Set &lt;code&gt;NOMAD_STORAGE_PATH&lt;/code&gt; to that exact same host path.&lt;/li&gt;
&lt;li&gt;Change the host side of the disk-collector mount to match.&lt;/li&gt;
&lt;li&gt;Start with &lt;code&gt;docker compose up -d&lt;/code&gt;, then check both content and disk usage in the interface.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If the library is empty, stop again and compare all three references with the actual directory containing the original files. For external or network storage, mount it on the host first; NOMAD does not configure the storage protocol itself. MySQL and Redis have separate data directories, so the content-storage setting is not a replacement for those mounts.&lt;/p&gt;

&lt;h2&gt;
  
  
  A small port-mapping check
&lt;/h2&gt;

&lt;p&gt;If host port 8080 is occupied, change only the left side of the mapping and update &lt;code&gt;URL&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"9090:8080"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Leave the container’s &lt;code&gt;PORT=8080&lt;/code&gt; unchanged.&lt;/p&gt;

&lt;p&gt;Finally, Docker availability alone does not make every NAS a supported target. NAS graphical stack imports are outside the documented support path, and Raspberry Pi/ARM was not officially tested or supplied with official images at the guide’s check time.&lt;/p&gt;

&lt;p&gt;The full Chinese step-by-step guide (install script or manual Compose, NAS / Raspberry Pi boundaries, troubleshooting) is here: &lt;a href="https://9012938178391.gumroad.com/l/tjlxtb" rel="noopener noreferrer"&gt;https://9012938178391.gumroad.com/l/tjlxtb&lt;/a&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>selfhosted</category>
      <category>linux</category>
      <category>homelab</category>
    </item>
    <item>
      <title>OpenMausBot on a VPS: Compose, HTTPS, and the ENGINES Rebuild Trap</title>
      <dc:creator>薛定谔的快乐</dc:creator>
      <pubDate>Mon, 09 Nov 2026 02:42:22 +0000</pubDate>
      <link>https://dev.to/9904099/openmausbot-on-a-vps-compose-https-and-the-engines-rebuild-trap-1hdl</link>
      <guid>https://dev.to/9904099/openmausbot-on-a-vps-compose-https-and-the-engines-rebuild-trap-1hdl</guid>
      <description>&lt;p&gt;This is a third-party deployment note, not official OpenMausBot documentation. It covers the guide’s Path B: a Linux VPS, a domain under your control, Docker Compose, and Caddy for HTTPS.&lt;/p&gt;

&lt;p&gt;The useful distinction is between pulling a prepared image and building one with your own configuration. Both use Compose, but they do not produce the same result when &lt;code&gt;ENGINES&lt;/code&gt; changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the network layout intact
&lt;/h2&gt;

&lt;p&gt;Start with Docker Engine and Compose V2. Point the domain’s A record at the VPS and allow inbound TCP 80 and 443. The hostname entered as &lt;code&gt;DOMAIN&lt;/code&gt; must not include &lt;code&gt;https://&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The supplied deployment has an unusual but deliberate layout: Caddy uses &lt;code&gt;network_mode: service:omb&lt;/code&gt;, sharing the application’s network namespace. Public port mappings therefore belong to &lt;code&gt;omb&lt;/code&gt;, even though Caddy handles HTTPS.&lt;/p&gt;

&lt;p&gt;Caddy forwards normal requests to the loopback application listener and &lt;code&gt;/hooks/*&lt;/code&gt; to the separate webhook listener. The supplied configuration also disables buffering for event streams.&lt;/p&gt;

&lt;p&gt;Never publish 8799/8800 to the internet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pulling an image is not configuring its contents
&lt;/h2&gt;

&lt;p&gt;From the repository’s &lt;code&gt;deploy/&lt;/code&gt; directory, copy &lt;code&gt;.env.example&lt;/code&gt; to &lt;code&gt;.env&lt;/code&gt; and edit the domain and engine selection. The standard prebuilt-image startup is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose pull omb &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; docker compose up &lt;span class="nt"&gt;-d&lt;/span&gt;
docker compose ps
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The expected state is &lt;code&gt;omb&lt;/code&gt; healthy and &lt;code&gt;caddy&lt;/code&gt; running. Open the HTTPS domain after Caddy has obtained its certificate. A pairing prompt is expected before login; it does not mean deployment failed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The concrete pitfall:&lt;/strong&gt; editing &lt;code&gt;ENGINES&lt;/code&gt; in &lt;code&gt;.env&lt;/code&gt; does not change an already-pulled image. Those engine command-line packages are baked into the image during its build. Pulling the prebuilt image retrieves whatever its own build included, not a new image tailored to the local &lt;code&gt;.env&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;To build with the configured engine list, run this from &lt;code&gt;deploy/&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose up &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="nt"&gt;--build&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The supplied Compose file already defines the build context and passes &lt;code&gt;ENGINES&lt;/code&gt; as a build argument. Installing the required command-line packages and logging into their accounts are separate steps: rebuilding handles the former, not the latter.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose the image reference deliberately
&lt;/h2&gt;

&lt;p&gt;At the guide’s check time, &lt;strong&gt;2026-11-06&lt;/strong&gt;, &lt;code&gt;:latest&lt;/code&gt; and &lt;code&gt;:v0.1.142&lt;/code&gt; had different index digests. They should not be treated as interchangeable references.&lt;/p&gt;

&lt;p&gt;The default Compose image follows &lt;code&gt;:latest&lt;/code&gt;. To pin the checked release, change &lt;code&gt;omb.image&lt;/code&gt; in &lt;code&gt;docker-compose.yml&lt;/code&gt; to &lt;code&gt;ghcr.io/milind-soni/openmausbot:v0.1.142&lt;/code&gt;, then run the pull-and-start command above. Pinning an equivalent digest is another option described in the guide. This image-reference choice is separate from building a customized image with &lt;code&gt;ENGINES&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pair, then preserve the data
&lt;/h2&gt;

&lt;p&gt;After completing the required account login inside the container, generate a pairing link:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose &lt;span class="nb"&gt;exec &lt;/span&gt;omb node dist-server/openmausbot.js pair &lt;span class="nt"&gt;--label&lt;/span&gt; &lt;span class="s2"&gt;"My MacBook"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Open the returned HTTPS link to connect the browser. Pairing is the login path; codes are single-use and expire after roughly five minutes.&lt;/p&gt;

&lt;p&gt;The container uses &lt;code&gt;HOME=/data&lt;/code&gt;, backed by the named &lt;code&gt;data&lt;/code&gt; volume. Application state and command-line credentials persist there. Before upgrades, back up the actual volume name: changing the Compose project name can change which volume the deployment uses. Stop &lt;code&gt;omb&lt;/code&gt; for the guide’s backup procedure, and keep the archive somewhere other than the VPS.&lt;/p&gt;

&lt;p&gt;The full Chinese step-by-step guide (Compose + Caddy HTTPS, pairing, backups, ARM notes) is here: &lt;a href="https://9012938178391.gumroad.com/l/hkvly" rel="noopener noreferrer"&gt;https://9012938178391.gumroad.com/l/hkvly&lt;/a&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>selfhosted</category>
      <category>devops</category>
      <category>linux</category>
    </item>
    <item>
      <title>Self-hosting SuperPlane: Pin the Release, Then Prove HTTPS Works</title>
      <dc:creator>薛定谔的快乐</dc:creator>
      <pubDate>Sat, 07 Nov 2026 01:23:44 +0000</pubDate>
      <link>https://dev.to/9904099/self-hosting-superplane-pin-the-release-then-prove-https-works-3fb4</link>
      <guid>https://dev.to/9904099/self-hosting-superplane-pin-the-release-then-prove-https-works-3fb4</guid>
      <description>&lt;p&gt;Getting containers to start is only half of a self-hosted deployment. The other half is making sure the hostname works from the public internet, the TLS certificate is valid, and GitHub can deliver events back to your installation.&lt;/p&gt;

&lt;p&gt;A dashboard that loads on your own machine does not prove any of those things.&lt;/p&gt;

&lt;p&gt;This walkthrough covers the main installation path on one Linux VM. Settle the package versions and public entry point first, then connect a repository. Troubleshooting every failure by trying a different image tag is a good way to lose track of what actually changed.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;This is a third-party deployment note, not official SuperPlane documentation. The version baseline comes from the full guide's November 5, 2026 review; it is not a fresh check of upstream releases or a claim about the latest version.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Check the host before downloading anything
&lt;/h2&gt;

&lt;p&gt;Start with a Linux VM you administer, using either &lt;strong&gt;amd64 or arm64&lt;/strong&gt;. You need Docker Engine, Compose v2, Bash, cURL, tar, and OpenSSL. The host must also reach GitHub Releases, ghcr.io, and Docker Hub over HTTPS; otherwise, installation can stall at the download stage.&lt;/p&gt;

&lt;p&gt;For the public entry point, use a domain you control and make sure &lt;strong&gt;TCP ports 80 and 443&lt;/strong&gt; reach the installation host. Every published A or AAAA record must point to the correct machine and remain reachable. Testing only whichever address your laptop prefers can miss a broken route.&lt;/p&gt;

&lt;p&gt;If another reverse proxy already owns those ports, resolve that conflict before installing. Do not stack another entry point on top and hope for the best.&lt;/p&gt;

&lt;p&gt;Size the machine for execution, not just for displaying the dashboard. The official sizing guidance carried into the full guide reserves approximately &lt;strong&gt;2 vCPU, 8 GB RAM, and 30 GB disk per concurrent runner&lt;/strong&gt;, excluding the core services. Set capacity around the resources actually available; copying defaults is not a performance guarantee.&lt;/p&gt;

&lt;p&gt;There is also an important trust boundary: &lt;strong&gt;Fleet Manager mounts &lt;code&gt;docker.sock&lt;/code&gt;&lt;/strong&gt;, giving it control over the host's Docker environment. Install it only on a machine you manage, with that level of access in mind.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Choose the application package, not just a release tag
&lt;/h2&gt;

&lt;p&gt;This note uses the &lt;strong&gt;v1.0.0 application package&lt;/strong&gt;, specifically the &lt;code&gt;superplane-single-host.tar.gz&lt;/code&gt; asset attached to that application release. Its accompanying components are &lt;strong&gt;Fleet Manager v0.1.6&lt;/strong&gt; and &lt;strong&gt;Runner v0.2.1&lt;/strong&gt;. Keep those together rather than independently upgrading the components.&lt;/p&gt;

&lt;p&gt;After extracting the archive, enter the &lt;code&gt;superplane&lt;/code&gt; directory and check that it contains:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;install.sh&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;docker-compose.yml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Caddyfile&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Before installing, compare these details with the upstream application release. The versions here are a documented baseline, not a statement that they are today's newest releases.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Run the installer and establish HTTPS
&lt;/h2&gt;

&lt;p&gt;From the installation directory, run:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;./install.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When prompted, enter a hostname such as &lt;code&gt;superplane.example.com&lt;/code&gt;, without an &lt;code&gt;https://&lt;/code&gt; prefix. The installer handles configuration and secrets, pulls images, starts services, and uses Caddy to request a certificate.&lt;/p&gt;

&lt;p&gt;Restrict access to the generated environment file and secrets directory, and back them up appropriately. They are not suitable attachments for a public troubleshooting issue or repository.&lt;/p&gt;

&lt;p&gt;Keep public exposure limited to the required ports, 80 and 443. Do not additionally expose the database or message-queue administration interfaces just to make debugging easier.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Verify the public endpoint before creating the owner account
&lt;/h2&gt;

&lt;p&gt;Check the containers first:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose ps
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then check &lt;code&gt;/health&lt;/code&gt; through your own HTTPS domain. The expected response is &lt;strong&gt;HTTP 200&lt;/strong&gt;. A running container is one useful signal, but it does not replace checking the externally reachable service.&lt;/p&gt;

&lt;p&gt;Once that works, open &lt;code&gt;/setup&lt;/code&gt; and create the owner account. For the community edition, choose &lt;strong&gt;Continue with Community&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;This ordering gives you a working foundation before you start repository authorization. Repeatedly trying the GitHub connection while the public endpoint is still broken only adds another moving part.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Connect GitHub through the interface
&lt;/h2&gt;

&lt;p&gt;Enter the workspace and follow &lt;strong&gt;Connect GitHub&lt;/strong&gt; to complete authorization or installation. Choose a repository for which you have sufficient permissions, then import work. Keep the connection scope small and start with a simple task.&lt;/p&gt;

&lt;p&gt;When configuring GitHub triggers, let the product create and manage the webhook. Do not bypass its authorization flow by guessing a callback URL from another article and pasting it into GitHub. Exact interface details depend on the installed version and official instructions.&lt;/p&gt;

&lt;p&gt;Treat service reachability and task execution as separate checks. If the interface works but no runner container appears, investigate the local fleet settings in the interface before reinstalling everything. Save the current configuration and logs first, then consult the relevant documentation section. Troubleshooting should not undo the parts that already work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two traps worth checking early
&lt;/h2&gt;

&lt;h3&gt;
  
  
  GitHub's “Latest” is not necessarily the single-host package
&lt;/h3&gt;

&lt;p&gt;The release marked &lt;strong&gt;Latest&lt;/strong&gt; may be a component tag rather than the application release containing the single-host archive. If the download looks wrong, check the tag and asset name first. Mixing Fleet Manager and Runner versions is not a fix for downloading the wrong package.&lt;/p&gt;

&lt;h3&gt;
  
  
  A certificate stays pending
&lt;/h3&gt;

&lt;p&gt;Check the domain's A and AAAA records, then confirm that ports 80 and 443 actually reach Caddy. Next, inspect its logs:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose logs caddy &lt;span class="nt"&gt;--tail&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;50
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Successful access from inside the host does not establish public reachability. Until HTTPS works, avoid treating the failure as a GitHub authorization problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  When you need the longer checklist
&lt;/h2&gt;

&lt;p&gt;This outline helps establish the installation order and prerequisites. For installation, capacity planning, acceptance checks, GitHub integration, and upgrade/uninstall boundaries in one place, the &lt;a href="https://9012938178391.gumroad.com/l/vpthly" rel="noopener noreferrer"&gt;full Chinese SuperPlane guide&lt;/a&gt; is a &lt;strong&gt;$9, docs-only guide written in Chinese&lt;/strong&gt;—not a software license, with no deployment service, ongoing operations, or availability guarantee included.&lt;/p&gt;

</description>
      <category>selfhosted</category>
      <category>docker</category>
      <category>devops</category>
      <category>github</category>
    </item>
    <item>
      <title>I shipped a $24 Notion Client &amp; Billing Board for freelancers</title>
      <dc:creator>薛定谔的快乐</dc:creator>
      <pubDate>Wed, 28 Oct 2026 05:46:47 +0000</pubDate>
      <link>https://dev.to/9904099/i-shipped-a-24-notion-client-billing-board-for-freelancers-38kn</link>
      <guid>https://dev.to/9904099/i-shipped-a-24-notion-client-billing-board-for-freelancers-38kn</guid>
      <description>&lt;p&gt;I got tired of tracking freelance clients and invoices across notes and spreadsheets, so I shipped a small Notion template.&lt;/p&gt;

&lt;p&gt;Client &amp;amp; Billing Board keeps clients, project work, and invoices in linked databases, with a simple cover dashboard for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;active clients&lt;/li&gt;
&lt;li&gt;unpaid invoice total&lt;/li&gt;
&lt;li&gt;this-month revenue&lt;/li&gt;
&lt;li&gt;overdue count&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It’s a digital Notion Duplicate (English UI, sample rows, short Getting Started). Fixed $24 on Gumroad — no custom consulting in this listing.&lt;/p&gt;

&lt;p&gt;Product: &lt;a href="https://9012938178391.gumroad.com/l/jhvrbe" rel="noopener noreferrer"&gt;https://9012938178391.gumroad.com/l/jhvrbe&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you already live in Notion and only need a billing board (not a full accounting app), feedback is welcome.&lt;br&gt;
Contact: &lt;a href="mailto:9904099@gmail.com"&gt;9904099@gmail.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>freelance</category>
      <category>showdev</category>
      <category>sideprojects</category>
    </item>
  </channel>
</rss>
