<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build-Log on Dendrite // Log</title><link>https://blog.hakvault.com/tags/build-log/</link><description>Recent content in Build-Log on Dendrite // Log</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.hakvault.com/tags/build-log/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up This Blog: A Log of the Build Log</title><link>https://blog.hakvault.com/2026/06/setting-up-this-blog-a-log-of-the-build-log/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.hakvault.com/2026/06/setting-up-this-blog-a-log-of-the-build-log/</guid><description>&lt;p>This blog exists because I wanted permanent documentation that nobody can take from me. Platforms get demonetized, algorithms shift, accounts get flagged — none of that happens to a folder of Markdown files sitting in a git repo I control. Fitting, then, that the first real post here is about standing the thing up. Wasn&amp;rsquo;t a clean one-shot deploy. Worth recording exactly where it went sideways.&lt;/p>
&lt;h2 id="the-stack-decision">The stack decision&lt;/h2>
&lt;p>Started by almost going down the Ghost-on-a-VPS route — self-hosted Ghost via Docker on Oracle&amp;rsquo;s free-tier cloud. Backed out of it once I was honest about what I actually wanted: zero ongoing maintenance. A VPS means an OS to patch, a Docker daemon to babysit, the occasional &amp;ldquo;why did my server stop responding&amp;rdquo; debugging session. None of that is what I&amp;rsquo;m here for.&lt;/p></description></item><item><title>Building and Shipping Dendrite RevShell</title><link>https://blog.hakvault.com/2026/06/building-and-shipping-dendrite-revshell/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.hakvault.com/2026/06/building-and-shipping-dendrite-revshell/</guid><description>&lt;p>I wanted a reverse shell payload reference for the brand — something in the same spirit as revshells.com, but mine: my domain, my design, my payload list. This is the build log.&lt;/p>
&lt;h2 id="why-build-this-instead-of-just-using-revshellscom">Why build this instead of just using revshells.com&lt;/h2>
&lt;p>Two reasons. First, it&amp;rsquo;s a genuinely useful tool to have under my own domain — a reference I control, that I can extend, that points back to HackVault instead of someone else&amp;rsquo;s project. Second, it was a small enough scope to actually finish. I&amp;rsquo;ve learned that the projects I ship are the small ones — narrow scope, clear &amp;ldquo;done&amp;rdquo; state, demoable the moment it&amp;rsquo;s live.&lt;/p></description></item></channel></rss>