Rename redacted-note class to note (reader callout, not redacted content)

This commit is contained in:
2026-09-11 22:57:30 +02:00
parent 2f8f1905ab
commit cd2bfa1a33
15 changed files with 15 additions and 15 deletions
+1 -1
View File
@@ -33,5 +33,5 @@ layout: base.njk
<li><strong>PyCharm</strong>, used the same way for Python projects.</li>
</ul>
<p class="redacted-note">This setup deliberately treats the dev VM as ephemeral infrastructure, not a pet, the philosophy is: keep state in Git, keep the VM replaceable, and let daily backups absorb the risk of giving an AI agent real write access to the system.</p>
<p class="note">This setup deliberately treats the dev VM as ephemeral infrastructure, not a pet, the philosophy is: keep state in Git, keep the VM replaceable, and let daily backups absorb the risk of giving an AI agent real write access to the system.</p>
</div>
+1 -1
View File
@@ -40,5 +40,5 @@ layout: base.njk
<li><strong>Advantage</strong>, simple backup via <code>mysqldump</code>, straightforward remote access configuration (bind-address, dedicated service users per consuming application), and one central database that multiple Docker containers on other hosts can connect to over the network instead of each running their own database container.</li>
</ul>
<p class="redacted-note">All three LXCs run exclusively on the main Proxmox host (PVE), not on pve2 or the Synology, they're intentionally kept centralized since they're few in number and don't need the multi-host redundancy that the Docker setup has. IPs, credentials and specific VMIDs are omitted here; only the reasoning behind the LXC-vs-Docker choice is shown.</p>
<p class="note">All three LXCs run exclusively on the main Proxmox host (PVE), not on pve2 or the Synology, they're intentionally kept centralized since they're few in number and don't need the multi-host redundancy that the Docker setup has. IPs, credentials and specific VMIDs are omitted here; only the reasoning behind the LXC-vs-Docker choice is shown.</p>
</div>