<?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>Forem: Diogo Abreu</title>
    <description>The latest articles on Forem by Diogo Abreu (@diogoabreudev).</description>
    <link>https://forem.com/diogoabreudev</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3882546%2Ff1912950-c1b3-4956-98c9-bc60b5201fe6.jpeg</url>
      <title>Forem: Diogo Abreu</title>
      <link>https://forem.com/diogoabreudev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/diogoabreudev"/>
    <language>en</language>
    <item>
      <title>How to safely parse, merge, or generate .env files (without uploading secrets online)</title>
      <dc:creator>Diogo Abreu</dc:creator>
      <pubDate>Fri, 17 Apr 2026 16:00:00 +0000</pubDate>
      <link>https://forem.com/diogoabreudev/how-to-safely-parse-merge-or-generate-env-files-without-uploading-secrets-online-1cbh</link>
      <guid>https://forem.com/diogoabreudev/how-to-safely-parse-merge-or-generate-env-files-without-uploading-secrets-online-1cbh</guid>
      <description>&lt;p&gt;Working with .env files is something we all do, but it’s surprisingly easy to make mistakes.&lt;/p&gt;

&lt;p&gt;Duplicate keys, malformed values, missing quotes… they can be annoying to debug.&lt;/p&gt;

&lt;p&gt;At some point I thought:&lt;br&gt;
“Why isn’t there a simple tool that does all the work for me?”&lt;/p&gt;

&lt;p&gt;Then I realized something else:&lt;br&gt;
An online .env viewer sounds like a &lt;strong&gt;terrible idea&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;If I saw one, I’d assume it’s stealing companys' keys.&lt;/p&gt;

&lt;p&gt;So I built one with a constraint:&lt;br&gt;
Everything must &lt;strong&gt;run 100% in the browser&lt;/strong&gt; and be &lt;strong&gt;100% safe&lt;/strong&gt;.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No uploads&lt;/li&gt;
&lt;li&gt;No backend&lt;/li&gt;
&lt;li&gt;No storage&lt;/li&gt;
&lt;li&gt;No network requests at all&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All very highlighted and verifiable through devtools.&lt;/p&gt;

&lt;p&gt;The result is a small tool that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Parses .env files instantly&lt;/li&gt;
&lt;li&gt;Detects duplicate keys&lt;/li&gt;
&lt;li&gt;Highlights syntax issues&lt;/li&gt;
&lt;li&gt;Shows everything in a clean table&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Additionally, I included some other pages to &lt;strong&gt;merge&lt;/strong&gt; multiple .env files together, or to &lt;strong&gt;generate&lt;/strong&gt; a fresh .env file with the most commonly used keys.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://env-tools.vercel.app/" rel="noopener noreferrer"&gt;https://env-tools.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d really appreciate some feedback, especially on how to make the “this is safe” part clearer. Hope this tool is useful and thank you very much in advance!&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>frontend</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
