<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docker on grainworks</title><link>https://grainworks.tech/tags/docker/</link><description>Recent content in Docker on grainworks</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 10 Jun 2026 16:00:00 -0400</lastBuildDate><atom:link href="https://grainworks.tech/tags/docker/index.xml" rel="self" type="application/rss+xml"/><item><title>Vaultwarden Migration &amp; Security Assessment</title><link>https://grainworks.tech/projects/vaultwarden-migration/</link><pubDate>Wed, 10 Jun 2026 16:00:00 -0400</pubDate><guid>https://grainworks.tech/projects/vaultwarden-migration/</guid><description>&lt;p&gt;&lt;strong&gt;Status: Migration from old instance complete. Security assessment under review.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;A thorough evaluation of the self-hosted Vaultwarden setup, including migration to a new server, comprehensive security assessment, replacement analysis, and alternative password management strategies.&lt;/p&gt;
&lt;h2 id="what-was-done"&gt;What Was Done&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Cloned the production database&lt;/strong&gt; from the UnRAID tower to the local Mini for redundancy&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Performed a security assessment&lt;/strong&gt; covering container hardening, backup strategy, TLS configuration, and access controls&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Evaluated beyond-Bitwarden alternatives&lt;/strong&gt; — what would it take to move away from Vaultwarden entirely? Including Passkey-first approaches, age-encrypted password stores (hermes-pass), and hardware-backed solutions&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Maintained a mirror&lt;/strong&gt; at &lt;code&gt;/Volumes/Mini_1Tb/Projects/vaultwarden-mirror/&lt;/code&gt; for development and testing&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="source-files"&gt;Source Files&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Main repo:&lt;/strong&gt; &lt;code&gt;/Volumes/Mini_1Tb/Projects/vaultwarden/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mirror (dev):&lt;/strong&gt; &lt;code&gt;/Volumes/Mini_1Tb/Projects/vaultwarden-mirror/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Security assessment:&lt;/strong&gt; &lt;code&gt;vaultwarden-replacement-security-assessment.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Replacement plan:&lt;/strong&gt; &lt;code&gt;vaultwarden-replacement-plan.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Beyond-Bitwarden analysis:&lt;/strong&gt; &lt;code&gt;vaultwarden-replacement-beyond-bitwarden.md&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="key-findings"&gt;Key Findings&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Current Vaultwarden deployment is stable but has hardening gaps&lt;/li&gt;
&lt;li&gt;Age-encrypted password stores (hermes-pass) offer a compelling alternative for CLI-centric workflows&lt;/li&gt;
&lt;li&gt;Passkey-first approaches are still maturing — Vaultwarden remains the better choice for shared/secrets management in the near term&lt;/li&gt;
&lt;li&gt;Hook scripts on the mirror enable custom pre/post-backup processing&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>