https://thequib.github.io/Rondo/blog/Recent content in Updates on Rondo DocsHugo -- gohugo.ioen-ushttps://thequib.github.io/Rondo/blog/v2.0.1/Mon, 04 Nov 2024 00:00:00 +0000https://thequib.github.io/Rondo/blog/v2.0.1/ <h1>Fixed</h1><p><code>config.yml.j2</code> now includes new variables with default values.</p>https://thequib.github.io/Rondo/blog/v2.1.0/Mon, 04 Nov 2024 00:00:00 +0000https://thequib.github.io/Rondo/blog/v2.1.0/ <h1>Fixed</h1><p>GPIO not cleaning up after container shutdown.</p>https://thequib.github.io/Rondo/blog/v2.0.0/Thu, 31 Oct 2024 00:00:00 +0000https://thequib.github.io/Rondo/blog/v2.0.0/ <h1>Added</h1><ul> <li>Added ability to add a status LED light</li> <li>Added ability to change LED pin</li> <li>Added ability to change button pin</li> </ul> <h1>Updated</h1><ul> <li>Updated <code>README.md</code>, now separates <em>required</em> and <em>optional</em> variables.</li> </ul>https://thequib.github.io/Rondo/blog/v1.1.1/Thu, 12 Sep 2024 00:00:00 +0000https://thequib.github.io/Rondo/blog/v1.1.1/ <h1>Removed</h1><p>Removed the upgrade action in the first step of the deployment playbook.</p>https://thequib.github.io/Rondo/blog/docsite/Sun, 08 Sep 2024 00:00:00 +0000https://thequib.github.io/Rondo/blog/docsite/ <p>When I first put Rondo together, the README made sense. It was a small project, the setup was straightforward enough, and a single markdown file felt like plenty. But as the project grew — more configuration options, Semaphore support, LED functionality, multiple deployment scenarios — the README started turning into a wall of text that was hard to navigate and harder to maintain.</p> <p>So I built a proper documentation site.</p> <h2>What&rsquo;s here<span class="hx:absolute hx:-mt-20" id="whats-here"></span> <a href="#whats-here" class="subheading-anchor" aria-label="Permalink for this section"></a></h2><p>The site covers everything you need to get Rondo running and configured:</p> <ul> <li><strong>Getting Started</strong> walks through hardware wiring and deploying with Ansible from scratch</li> <li><strong>Configuration</strong> breaks down every variable in <code>config.yml</code>, what it does, and when you&rsquo;d use it</li> <li><strong>Semaphore</strong> covers managing multi-Pi deployments through Ansible Semaphore, including per-host and global variable setup</li> </ul> <p>It&rsquo;s the same information that was in the README, just organized in a way that&rsquo;s actually easy to navigate — especially once you&rsquo;re past the initial setup and just need to look something up quickly.</p> <h2>The README isn&rsquo;t going away<span class="hx:absolute hx:-mt-20" id="the-readme-isnt-going-away"></span> <a href="#the-readme-isnt-going-away" class="subheading-anchor" aria-label="Permalink for this section"></a></h2><p>The README will stick around as a quick project summary and a pointer to this site. But going forward, all documentation updates will happen here. If something&rsquo;s missing, outdated, or unclear, this is where the fix will land — not in the README.</p> <h2>What&rsquo;s next<span class="hx:absolute hx:-mt-20" id="whats-next"></span> <a href="#whats-next" class="subheading-anchor" aria-label="Permalink for this section"></a></h2><p>I always say, there&rsquo;s always something to document, so I will keep this site updated and moving forward where I see a need. If there&rsquo;s something specific you&rsquo;d like covered, open an issue on the <a href="https://github.com/TheQuib/Rondo"target="_blank" rel="noopener">GitHub repo</a> with the <code>documentation</code> tag.</p>https://thequib.github.io/Rondo/blog/v1.0.1/Sun, 08 Sep 2024 00:00:00 +0000https://thequib.github.io/Rondo/blog/v1.0.1/ <h1>Fixed</h1><p>Updating <code>config.yml</code> not updating environment variables. Added <code>--force-restart</code> to container start check.</p>