<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>afterconfig on Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/afterconfig/</link>
    <description>Recent content in afterconfig on Aftermarket.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aftermarket.dev/tags/afterconfig/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AfterConfig Adds TOML Overlays That Keep Every Comment</title>
      <link>https://aftermarket.dev/afterconfig-adds-toml-overlays-that-keep-every-comment/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterconfig-adds-toml-overlays-that-keep-every-comment/</guid>
      <description>Aftermarket 0.7.0 teaches AfterConfig to read and write TOML. That&amp;rsquo;s the config format of a lot of newer software: Rust and Python tools, Go services, Hugo, plenty of daemons. Their vendors replace config.toml on every upgrade, same as everyone else.
An overlay works the same way it does for JSON, YAML and .env. You list your changes by dot path, each one guarded by the value it expects, and config apply writes the result to a separate file.</description>
    </item>
    
    <item>
      <title>AfterConfig Released to Change Vendor Config Files Without Editing Them</title>
      <link>https://aftermarket.dev/afterconfig-released-to-change-vendor-config-files-without-editing-them/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterconfig-released-to-change-vendor-config-files-without-editing-them/</guid>
      <description>Aftermarket 0.4.0 adds AfterConfig, run as aftermarket config. It&amp;rsquo;s for the config file a vendor ships with its app, the one you have to change and every upgrade overwrites.
The usual fix is to edit the file and keep a note somewhere. Then the upgrade lands, the note gets forgotten, and the app runs on vendor defaults again. Or worse, someone copies the old file back over the new one and wipes out a setting the vendor added on purpose.</description>
    </item>
    
    <item>
      <title>Case Study: Getting Through a Vendor Upgrade With AfterConfig Guards</title>
      <link>https://aftermarket.dev/case-study-getting-through-a-vendor-upgrade-with-afterconfig-guards/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-getting-through-a-vendor-upgrade-with-afterconfig-guards/</guid>
      <description>This case uses the examples/vendor-app folder that ships in every download archive, so you can run each step yourself. The commands and output below come from a real run of the downloaded aftermarket 0.4.0.
The situation A team runs a vendor&amp;rsquo;s app. It reads config.json, and each upgrade replaces that file. The team needs seven changes:
a longer timeout more workers JSON logs no telemetry their own database password a bigger connection pool a body limit the vendor doesn&amp;rsquo;t offer yet They keep those changes in overlay.</description>
    </item>
    
    <item>
      <title>Case Study: Keeping Changes to a Vendor TOML Config Through an Upgrade</title>
      <link>https://aftermarket.dev/case-study-keeping-changes-to-a-vendor-toml-config-through-an-upgrade/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-keeping-changes-to-a-vendor-toml-config-through-an-upgrade/</guid>
      <description>This case uses the examples/vendor-app-toml folder that ships in every download archive, so you can run each step yourself. The vendor app is a stand-in. The commands and output below come from a real run of the downloaded aftermarket 0.7.0.
The situation A team runs a vendor&amp;rsquo;s app that reads config.toml. The vendor writes good comments in that file, and replaces it on every upgrade. The team needs seven changes: a longer timeout, more workers, JSON logs, no telemetry, their own database password, a bigger pool, and the weekly report moved to Sunday.</description>
    </item>
    
    <item>
      <title>How AfterConfig Was Tested to Never Write a Vendor Config File</title>
      <link>https://aftermarket.dev/how-afterconfig-was-tested-to-never-write-a-vendor-config-file/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/how-afterconfig-was-tested-to-never-write-a-vendor-config-file/</guid>
      <description>AfterConfig makes four promises, and the tests go after each one. It never writes the vendor&amp;rsquo;s file. It never changes what the overlay doesn&amp;rsquo;t name. A failed apply leaves the old output alone. And it never prints a secret.
The vendor&amp;rsquo;s file The test makes the vendor&amp;rsquo;s file read-only and runs every command against it. Then it names that file as the output in six ways: directly, through a symbolic link, through a hard link, through a linked folder, as a relative path, and with a .</description>
    </item>
    
    <item>
      <title>How TOML Support in AfterConfig Was Tested</title>
      <link>https://aftermarket.dev/how-toml-support-in-afterconfig-was-tested/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/how-toml-support-in-afterconfig-was-tested/</guid>
      <description>TOML in AfterConfig makes one promise on top of the old ones: the output is the vendor&amp;rsquo;s file with only your changes in it. Comments, spacing and every untouched line come through byte for byte. The tests try to catch it breaking that, or getting a value wrong while keeping the layout.
Reading TOML the way the spec does AfterConfig has its own TOML reader, since the project uses no outside libraries.</description>
    </item>
    
  </channel>
</rss>
