<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on Lixen</title><link>https://lixen.com/tags/devops/</link><description>Recent content in Devops on Lixen</description><generator>Hugo</generator><language>en-us</language><copyright>Lixen</copyright><lastBuildDate>Thu, 30 Oct 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://lixen.com/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Shell Execution Methods: An Overview</title><link>https://lixen.com/blog/002-shell_execution_methods/</link><pubDate>Thu, 30 Oct 2025 00:00:00 +0000</pubDate><guid>https://lixen.com/blog/002-shell_execution_methods/</guid><description>&lt;p&gt;Shell execution methods determine process creation, environment inheritance, and resource management. Each method serves specific operational requirements.&lt;/p&gt;</description></item><item><title>The Evolution of LogWisp: From a Simple Script to a Flexible Log Transport System</title><link>https://lixen.com/blog/001-logwisp/</link><pubDate>Fri, 24 Oct 2025 00:00:00 +0000</pubDate><guid>https://lixen.com/blog/001-logwisp/</guid><description>&lt;p&gt;LogWisp was born from a familiar devops frustration: the daily ritual of SSHing into multiple servers to tail and grep log files!
While powerful, enterprise-grade logging platforms exist, they often felt like overkill for my small projects and low traffic use cases. I wanted a simple, self-contained, single-binary solution that could stream, aggregate, and filter logs with minimal fuss. This is the story of how that idea evolved into a flexible, pipeline-based log transport system.&lt;/p&gt;</description></item></channel></rss>