<?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>Cli-Tip on taude.xyz</title><link>http://taude.xyz/tags/cli-tip/</link><description>Recent content in Cli-Tip on taude.xyz</description><generator>Hugo</generator><language>en-us</language><copyright>Todd</copyright><lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://taude.xyz/tags/cli-tip/index.xml" rel="self" type="application/rss+xml"/><item><title>Local Dev Secret Management with 1Password and Bitwarden</title><link>http://taude.xyz/posts/local-dev-secret-management-with-1password-and-bitwarden/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>http://taude.xyz/posts/local-dev-secret-management-with-1password-and-bitwarden/</guid><description>&lt;p&gt;Most developers have a graveyard of dotfiles, &lt;code&gt;.env&lt;/code&gt; files, and Slack DMs containing tokens that were supposed to be temporary. This post describes the pattern I use to keep all local dev secrets in a password manager and inject them into my shell on demand — nothing sensitive ever touches disk.&lt;/p&gt;
&lt;p&gt;The full setup lives in my &lt;a href="https://github.com/taudep/dot-local"&gt;dot-local repo on GitHub&lt;/a&gt;, including the helper functions and new-machine setup guide.&lt;/p&gt;
&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;I work across multiple machines: a work Mac that uses 1Password and a personal Mac that uses Bitwarden. I needed a single pattern that worked on both without maintaining two separate codebases or hardcoding tool-specific logic everywhere.&lt;/p&gt;</description></item></channel></rss>