Local Markdown Folder ➔ Git Commit/Push via GitHub CLI (gh) ➔ Private GitHub Repository ➔ Cloudflare Pages Build Engine ➔ Private Subdomain Protected by Cloudflare Access (Zero Trust).
Local Setup: Native binary Extended version of Hugo installed on
Ubuntu (sudo apt install hugo). Main configuration maintained in hugo.toml using the Hugo Learn Theme attached as a Git Submodule.
Version Management: Hugo v0.123+ introduced a strict breaking
change regarding virtual nested sections. To prevent internal page rendering panics (e.g., invalid memory address or nil pointer dereference), every subdirectory inside content/ must contain a valid _index.md file to explicitly declare it as a physical section.
Access Hardening: Secured utilizing Cloudflare Zero Trust Access
policies. Configured with a default-deny block, requiring identity confirmation via single-use pins sent directly to the administrator's secure email.
Isolation Strategy: Dependencies must reside within a dedicated,
local virtual environment container managed via the venv module.
Core Command Phrase Functional Intent & Operation
python3 -m venv .venv Spins up a localized python container root directly within the target project workspace.
source .venv/bin/activate Shifts active path environment variables, routing subsequent pip packages natively into isolation.
⚠️ SYSTEM ADMINISTRATOR REFRESHER / TO REMEMBER
Manual Testing Prerequisites:
Whenever interacting, executing, or patching the automation engine manually via terminal, you MUST step inside the parent scope and initialize the virtual environment framework explicitly:
cd ~/Projects/calendar-automation
source .venv/bin/activateBackground Automation Design (Cron Execution):
When migrating this script to a continuous background cron daemon, do not use system-wide paths or invoke standard activate utilities. Instead, bypass activation mechanics completely by referencing the absolute path of the environment's internal native execution binary directly:
*/15 * * * * /home/aztechguy/Projects/calendar-automation/.venv/bin/python /home/aztechguy/Projects/calendar-automation/buffer_automation.py
Since you’ve already dipped your toes into both, the goal here is moving from "installed" to "actionable insights."
Wazuh (SIEM): We can deploy the Wazuh manager via Docker on Ubuntu. Instead of just letting logs sit there, we'll focus on deploying the Wazuh agent to your endpoints and configuring active response rules (e.g., if an IP triggers multiple failed SSH logins on your server, Wazuh automatically drops that IP into iptables or tcpwrappers to block it).
OpenVAS: Rather than running it manually on Kali every time, we can look at setting up a scheduled greenbone vulnerability scan that targets your internal lab subnet weekly, exporting the results directly into your Wazuh dashboard for a unified security pane.