Finn Kowalski — Site Reliability Engineer
Product & Engineering

Finn Kowalski — Site Reliability Engineer

Skip to main content
< All Topics
Print

Finn Kowalski — Site Reliability Engineer

Title: Site Reliability / DevOps Engineer Department: Product & Engineering Division — Server Management Reports to: Jordan Calloway — Director of Product & Engineering

About

Finn is responsible for the availability, performance, and operational correctness of every running Patriot University service — production and local development alike. On the production side, that means the cPanel shared host at s15114.usc1.stableserver.net (patriot.university, api.patriot.university): the Passenger/lswsgi FastAPI backend under ~/papi/, the WordPress docroot at ~/public_html/, LiteSpeed cache configuration, SSH key management, and FTP sub-account access. Locally, three macOS launch agents (com.iti.patriot-publish-gui on port 8766, com.iti.patriot-tracker on port 5050, com.iti.patriot-api on port 8000) are governed by launchd plists with KeepAlive.SuccessfulExit = false; Finn maintains those plists, manages service restarts via launchctl stop/start, and monitors stdout/stderr log streams. He also oversees the Docker stack (infrastructure/) used for the n8n-dify workflow automation layer and ensures environment variables are correctly propagated across all service boundaries.

What They Do

  • Manages the production cPanel environment: SSH access, file permissions, ~/papi/ FastAPI layout, WordPress docroot health, and passenger_wsgi.py reload cycles
  • Owns the three launchd service plists (com.iti.patriot-{publish-gui,tracker,api}.plist) — authoring, loading, unloading, and version-controlling them in ~/Library/LaunchAgents/
  • Monitors all service log streams (logs/publish-gui-stdout.log, logs/tracker-stdout.log, logs/patriot-api-stdout.log) and escalates anomalies to the Director of Product & Engineering
  • Manages the LiteSpeed CSS exclusion configuration for the patriot-university-theme (optm-css_exc, optm-ucss_file_exc_inline) and coordinates wp litespeed-purge all after theme CSS deploys
  • Maintains the Docker Compose stack for the local infrastructure layer (infrastructure/) and ensures the n8n-dify services are healthy
  • Rotates .env credentials on schedule, validates that no secrets appear in git history, and coordinates SSH key rotation with the Security Architect

When They Get Involved

Finn is the first responder for any service outage — the live site returning 5xx errors, a local dev service failing to restart, a Passenger backend not reloading after a deploy, or log streams going silent. He is also involved in every production deploy (coordinating the rsync-and-purge sequence with the WordPress Engineer) and whenever a new environment variable is required by any script or service.

Works Closely With

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?
Table of Contents