<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Go on Martin Heck</title>
    <link>https://d696162b.martinheck-dev.pages.dev/tags/go/</link>
    <description>Recent content in Go on Martin Heck</description>
    <generator>Hugo -- 0.147.8</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 13 Oct 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://d696162b.martinheck-dev.pages.dev/tags/go/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Application configuration in Go</title>
      <link>https://d696162b.martinheck-dev.pages.dev/posts/go-basics/app-config/</link>
      <pubDate>Sun, 13 Oct 2024 00:00:00 +0000</pubDate>
      <guid>https://d696162b.martinheck-dev.pages.dev/posts/go-basics/app-config/</guid>
      <description>&lt;p&gt;Making applications configurable is a best practice and allows the same binary to be used in different environments and scenarios. Common examples are database (DB) connection strings and credentials to access other services. More information about the general concept can be found on &lt;a href=&#34;https://12factor.net/config&#34;&gt;The Twelve-Factor App&lt;/a&gt;. In this post, I will give a quick overview of the approaches I often use in Go and give some guidelines on when to use which.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
