Build Log

Barndoor knowledge base expanded

Expanded Barndoor’s local knowledge base so the Discord bot can return and search more useful infrastructure documentation from the server itself.

The knowledge files now include deeper notes for services, networking, backups, commands, recovery, and websites. This makes /notes, /searchnotes, and /addnote more useful during normal maintenance, troubleshooting, and recovery work.

I also added a new websites topic that documents tylerrodgers.space, TM44.link, Caddy, website file paths, the build log watcher, and the hidden recovery guide. Barndoor can now return this topic directly with /notes topic: websites.

Hidden Barndoor recovery guide created

Added a private recovery guide for Barndoor as a hidden direct URL. The page documents important restore locations, backup workflows, service checks, and verification steps for recovering the project if something breaks.

The guide is intentionally not linked from the public homepage, Barndoor page, Now page, TM44.link, or sitemap. It exists as a private reference for recovery planning without adding clutter to the public site navigation.

Barndoor enters the admin assistant phase

Barndoor has grown from a self-hosted Ubuntu server into a working personal infrastructure platform. It now hosts my websites, runs Docker services, powers local AI through Ollama, monitors public endpoints, and connects to Discord through the Barndoor bot.

The biggest change in this phase is that Barndoor is no longer just something I manage manually over SSH. The Discord bot now acts as an owner-only operations panel with commands for checking system health, service status, disk usage, network connectivity, logs, restarts, backups, GPU status, model settings, and hosted website status.

I also added a local knowledge system for Barndoor. The bot can now read fixed notes with /notes, search infrastructure documentation with /searchnotes, and append new notes from Discord with /addnote. This creates a simple read, search, and write workflow for documenting services, recovery steps, network details, backups, and command references as the project grows.

Backup automation is now in place as well. Barndoor creates daily configuration backups, reports backup status from Discord, and runs retention cleanup so old config backups do not pile up forever. Helper scripts were organized into a dedicated scripts folder, aliases were updated, and project notes were refreshed to reflect the current structure.

The public website has also become part of the system. The homepage, Now page, Build Log, and Barndoor project page have been updated to document the current state of the project. A build log notification watcher now checks for new build log updates and posts a polished Discord notification when the page changes, with a toggle command for turning those notifications on or off.

At this point, Barndoor has reached a useful milestone: it is a self-hosted server, a local AI platform, a website host, a monitoring environment, a Discord operations bot, and the beginning of a personal knowledge base. The next phase will focus on refining the documentation, improving recovery notes, and slowly turning Barndoor into a more capable AI-assisted system administration project.

Barndoor knowledge editing added

Added /addnote to the Barndoor Discord bot so I can append new information to the local knowledge files directly from Discord.

Combined with /notes and /searchnotes, this creates a simple read, search, and write workflow for Barndoor’s project-specific infrastructure documentation.

This makes the knowledge base easier to maintain while I’m actively working on the server. Instead of SSHing in every time I want to record a recovery note, service detail, backup reminder, or command reference, I can now add it from Discord.

Barndoor knowledge notes added

Added a local Barndoor knowledge folder and new Discord commands that let the bot return and search project-specific infrastructure notes.

The new /notes command returns fixed notes by topic, while /searchnotes searches across the local knowledge files. Current topics include services, network, recovery, backups, and commands.

This is the first step toward giving Barndoor more awareness of its own environment, including the services it runs, the ports it uses, recovery steps, backup locations, and local admin shortcuts.

Barndoor admin toolkit added

Expanded the Barndoor Discord bot with an owner-only server administration toolkit for monitoring, diagnostics, and basic service recovery from Discord.

New commands now let me check overall system health, view service and container status, inspect disk usage, test network and Ollama connectivity, read recent logs, restart approved services, and check backup status.

This creates the first full admin loop for Barndoor: check the system, inspect the problem, and recover a service without immediately needing to SSH into the server.

Local website migration to Barndoor

Migrated tylerrodgers.space and TM44.link from hosted web services to Barndoor, a locally hosted Ubuntu server running Docker, Caddy, and HTTPS.

This included DNS cleanup, router port forwarding, Caddy reverse proxy setup, production TLS certificates, and local firewall tightening.

TM44.link short-link hub

Turned TM44.link into both a public link hub and a short-link redirect domain for my active projects and build-log pages.

Current short links include /now, /buildlog, /barndoor, /haystack, and /me.

Barndoor Discord operations commands

Added operational commands to the Barndoor Discord bot so I can check site status, public links, host uptime, service health, GPU status, and active model information from Discord.

Commands added or improved include /websites, /links, /uptime, /report, and /help.

Dedicated project pages

Added standalone project pages for Barndoor and Haystack so each project has a clearer overview, current stack, next steps, and direct short-link destination.

Planned build-log topics

• How Barndoor is hosted on local hardware.
• How the Discord bot checks website and system status.
• How TM44.link redirects are managed through Caddy.
• How monitoring, backups, and recovery notes are organized.