<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scripting on Вороний блог | Linux и IT</title><link>https://r4ven.me/en/tags/scripting/</link><description>Recent content in Scripting on Вороний блог | Linux и IT</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 31 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://r4ven.me/en/tags/scripting/index.xml" rel="self" type="application/rss+xml"/><item><title>Bash: Generating configs with envsubst, here document, and here string</title><link>https://r4ven.me/en/automation/bash-generaciya-konfigov-cherez-envsubst-here-document-i-here-string/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://r4ven.me/en/automation/bash-generaciya-konfigov-cherez-envsubst-here-document-i-here-string/</guid><description>&lt;strong&gt;Greetings! &lt;i class="fa-solid fa-crow"&gt;&lt;/i&gt;
&lt;/strong&gt;

&lt;p&gt;In this note, we will briefly look at a few simple ways to build a config from a Bash script using &lt;code&gt;here document&lt;/code&gt;, &lt;code&gt;here string&lt;/code&gt;, and &lt;code&gt;envsubst&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;I probably would not call this full-fledged templating. It is more like regular text file generation with variable substitution. But in practice, this is usually enough: create a config on the first container startup, substitute a domain, port, path to the working directory, or SMTP parameters.&lt;/p&gt;</description></item></channel></rss>