<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Portfolio on Logos Tech Systems</title><link>https://logostechsystems.com/portfolio/</link><description>Recent content in Portfolio on Logos Tech Systems</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 18 Apr 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://logostechsystems.com/portfolio/index.xml" rel="self" type="application/rss+xml"/><item><title>Publishing a Site From a Proxmox LXC With No Inbound Ports</title><link>https://logostechsystems.com/portfolio/proxmox-lxc-cloudflare-tunnel/</link><pubDate>Sat, 18 Apr 2026 00:00:00 -0500</pubDate><guid>https://logostechsystems.com/portfolio/proxmox-lxc-cloudflare-tunnel/</guid><description>&lt;h2 id="the-goal">The goal&lt;/h2>
&lt;p>Host a public website on infrastructure we control, without opening any inbound port on the firewall and without exposing a server address that can be scanned or attacked directly.&lt;/p></description></item><item><title>Building a Support Queue That Produces Audit Evidence</title><link>https://logostechsystems.com/portfolio/ticketing-with-sla-tracking/</link><pubDate>Sat, 04 Apr 2026 00:00:00 -0500</pubDate><guid>https://logostechsystems.com/portfolio/ticketing-with-sla-tracking/</guid><description>&lt;h2 id="the-goal">The goal&lt;/h2>
&lt;p>Every support request should be traceable: who asked, when, what was done, who did it, and when it was closed. That&amp;rsquo;s obviously good for service quality. It&amp;rsquo;s also evidence, which matters more than most people realize.&lt;/p></description></item><item><title>Endpoint Monitoring and Patch Automation Across a Mixed Fleet</title><link>https://logostechsystems.com/portfolio/endpoint-monitoring-and-patch-automation/</link><pubDate>Sat, 21 Mar 2026 00:00:00 -0500</pubDate><guid>https://logostechsystems.com/portfolio/endpoint-monitoring-and-patch-automation/</guid><description>&lt;h2 id="the-goal">The goal&lt;/h2>
&lt;p>Know what&amp;rsquo;s on the network, keep it patched, and hear about failures before a user does. It sounds simple, and it&amp;rsquo;s where most environments fall short. Usually the tooling only covers part of the fleet: one tool for servers, another for laptops, and nothing at all for the machine someone set up two years ago and never enrolled.&lt;/p></description></item></channel></rss>