I build and operate Linux services, backend tools and game-server infrastructure. My work ranges from Docker Compose preflight checks to production troubleshooting, APIs and automation.

I also contribute fixes upstream: interval scheduling in Tokio, Unicode content search in Linux Mint's Nemo, and better game-server monitoring in LinuxGSM. I care about fixing the underlying problem and leaving useful tests behind.

• Linux infrastructure: VPS administration, containers, reverse proxies, backup and restore workflows, CI, monitoring and production troubleshooting.
• Web platforms and automation: publishing systems, operational dashboards, bots, API integrations and internal tools.
• Game servers: operating Minecraft and Rust environments, dealing with performance, configuration, plugins and service reliability.

Some of these systems are private or tied to specific projects, so their source code isn't here. The public projects and contributions below are easier to inspect.

A read-only Linux CLI for checking Docker Compose projects before deployment. It flags host port conflicts and missing bind-mount paths, and can compare planned changes with running containers.

A Python integration for MCP-compatible clients working with WISP game panels. It covers server resources, files, console commands, backups and databases, with permission controls for sensitive actions. The code is public under the PolyForm Noncommercial license.

Selected changes merged into independent upstream projects:

• Tokio #8385 · Rust — fixed interval deadline overflow for extreme durations, including tests for reset and missed-tick strategies.
• Nemo (Linux Mint) #3829 · C — restored Unicode content search and added a regression test for combining characters.
• LinuxGSM #5111 · Shell — improved failed game-server health checks with local listener and port diagnostics.
• tower-http #728 · Rust — made directory trailing-slash redirects configurable while preserving existing defaults.
• River #1359 · Go — prevented recurring jobs from advancing their schedule after failed batch insertion, with regression coverage.

I'm interested in good ideas, especially when there's a difficult technical problem to untangle. I'm happy to review an approach, share a second opinion or contribute a fix to a project I find worthwhile, even when there's no paid work involved.

For infrastructure work, backend integrations or agency subcontracting, find me at vitrine.bar.