<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Linux on Vladyslav Rovnyi</title>
    <link>https://vladyslavrov.com/tags/linux/</link>
    <description>Recent content in Linux on Vladyslav Rovnyi</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 26 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vladyslavrov.com/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why I Chose Debian 13 for My VPS</title>
      <link>https://vladyslavrov.com/blog/why-i-chose-debian-for-my-vps/</link>
      <pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://vladyslavrov.com/blog/why-i-chose-debian-for-my-vps/</guid>
      <description>&lt;p&gt;I recently set up a VPS for personal projects — hosting tools, running monitoring stacks, experimenting with security setups. The first decision was the OS, and after going back and forth I settled on Debian 13.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s why.&lt;/p&gt;
&lt;h2 id=&#34;stability-you-can-trust&#34;&gt;Stability you can trust&lt;/h2&gt;
&lt;p&gt;Debian&amp;rsquo;s reputation for stability isn&amp;rsquo;t marketing — it&amp;rsquo;s real. The release cycle is slow on purpose. Packages are tested heavily before they hit stable, and once they&amp;rsquo;re there they basically don&amp;rsquo;t change. That means I can leave the server running for months without worrying about a routine update breaking something at 2 AM.&lt;/p&gt;</description>
      <content>&lt;p&gt;I recently set up a VPS for personal projects — hosting tools, running monitoring stacks, experimenting with security setups. The first decision was the OS, and after going back and forth I settled on Debian 13.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s why.&lt;/p&gt;
&lt;h2 id=&#34;stability-you-can-trust&#34;&gt;Stability you can trust&lt;/h2&gt;
&lt;p&gt;Debian&amp;rsquo;s reputation for stability isn&amp;rsquo;t marketing — it&amp;rsquo;s real. The release cycle is slow on purpose. Packages are tested heavily before they hit stable, and once they&amp;rsquo;re there they basically don&amp;rsquo;t change. That means I can leave the server running for months without worrying about a routine update breaking something at 2 AM.&lt;/p&gt;
&lt;p&gt;For a personal server I rarely touch, that matters a lot.&lt;/p&gt;
&lt;h2 id=&#34;the-package-ecosystem-is-huge&#34;&gt;The package ecosystem is huge&lt;/h2&gt;
&lt;p&gt;This is the big one for me. &lt;code&gt;apt&lt;/code&gt; has basically everything I need:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Security tools (&lt;code&gt;nmap&lt;/code&gt;, &lt;code&gt;wireshark&lt;/code&gt;, &lt;code&gt;tcpdump&lt;/code&gt;, &lt;code&gt;fail2ban&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Monitoring (&lt;code&gt;prometheus&lt;/code&gt;, &lt;code&gt;node-exporter&lt;/code&gt;, &lt;code&gt;grafana&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;The whole ELK stack&lt;/li&gt;
&lt;li&gt;Docker, podman, and the usual container tools&lt;/li&gt;
&lt;li&gt;Reverse proxies (&lt;code&gt;nginx&lt;/code&gt;, &lt;code&gt;caddy&lt;/code&gt;, &lt;code&gt;haproxy&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Pretty much every language runtime&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Most tutorials and docs assume Debian or Ubuntu (which is downstream of Debian). When I follow a guide, &lt;code&gt;apt install&lt;/code&gt; usually just works — no hunting for community repos, no compiling from source, no weird package conflicts.&lt;/p&gt;
&lt;h2 id=&#34;compatibility-everywhere&#34;&gt;Compatibility everywhere&lt;/h2&gt;
&lt;p&gt;Because so much of the Linux world is built on top of Debian, knowledge and tools transfer easily:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Kali, Parrot, and most security-focused distros are Debian-based&lt;/li&gt;
&lt;li&gt;Ubuntu LTS is essentially Debian with extra polish&lt;/li&gt;
&lt;li&gt;Most Docker base images are &lt;code&gt;debian:slim&lt;/code&gt; or &lt;code&gt;ubuntu&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Configuration management tools (Ansible, etc.) treat it as first-class&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If a script works on my laptop or in a CTF lab, it almost certainly works on the VPS too.&lt;/p&gt;
&lt;h2 id=&#34;why-debian-13-specifically&#34;&gt;Why Debian 13 specifically&lt;/h2&gt;
&lt;p&gt;Debian 13 (&amp;ldquo;Trixie&amp;rdquo;) brings newer kernels and updated userspace without giving up the stability I want. Modern hardware support is better, container tooling is current, and the security backports keep things patched without forcing me into bleeding-edge versions.&lt;/p&gt;
&lt;p&gt;For a server that needs to last, that combination is hard to beat.&lt;/p&gt;
&lt;h2 id=&#34;what-i-run-on-it&#34;&gt;What I run on it&lt;/h2&gt;
&lt;p&gt;Right now the VPS hosts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A small monitoring stack&lt;/li&gt;
&lt;li&gt;A few personal services behind a reverse proxy&lt;/li&gt;
&lt;li&gt;Some honeypot experiments&lt;/li&gt;
&lt;li&gt;Cron jobs and scripts for things I want available 24/7&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Everything was set up using packages from the standard Debian repos. No custom builds, no weird workarounds.&lt;/p&gt;
&lt;h2 id=&#34;final-thoughts&#34;&gt;Final thoughts&lt;/h2&gt;
&lt;p&gt;Pick whatever distro you want — Linux is Linux, and there&amp;rsquo;s no objectively wrong choice. But for a server that should &lt;em&gt;just work&lt;/em&gt;, Debian is hard to argue with. It&amp;rsquo;s stable, predictable, well-documented, and compatible with almost everything.&lt;/p&gt;
&lt;p&gt;For me, that was enough.&lt;/p&gt;
</content>
    </item>
    
  </channel>
</rss>
