<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Toml on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/toml/</link>
    <description>Recent content in Toml on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/toml/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted YAML Data Processors: yq vs dasel Comparison Guide</title>
      <link>https://www.pistack.xyz/posts/2026-06-17-self-hosted-yaml-data-processors-yq-vs-dasel/</link>
      <pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-17-self-hosted-yaml-data-processors-yq-vs-dasel/</guid>
      <description>&lt;h2 id=&#34;why-use-command-line-data-format-processors&#34;&gt;Why Use Command-Line Data Format Processors?&lt;/h2&gt;&#xA;&lt;p&gt;Modern DevOps workflows involve juggling YAML, JSON, TOML, CSV, and XML configuration files. Manually editing these formats is error-prone, and writing custom scripts for each transformation is inefficient. Tools like &lt;strong&gt;yq&lt;/strong&gt; and &lt;strong&gt;dasel&lt;/strong&gt; provide &lt;code&gt;jq&lt;/code&gt;-like query and transformation capabilities across multiple data formats, making them indispensable for Infrastructure as Code, CI/CD pipelines, and configuration management.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
