<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Linux on Alfred van Ster</title><link>https://avanster.tech/tags/linux/</link><description>Recent content in Linux on Alfred van Ster</description><generator>Hugo -- 0.160.1</generator><language>en-us</language><lastBuildDate>Wed, 01 Jan 2025 17:00:00 +0000</lastBuildDate><atom:link href="https://avanster.tech/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing the Perimeter: Why I chose a VPS over Shared Hosting</title><link>https://avanster.tech/posts/securing-the-perimeter/</link><pubDate>Wed, 01 Jan 2025 17:00:00 +0000</pubDate><guid>https://avanster.tech/posts/securing-the-perimeter/</guid><description>&lt;p&gt;Most portfolios live on shared hosting—cheap, easy, but restricted. For my infrastructure, I chose a &lt;strong&gt;Virtual Private Server (VPS)&lt;/strong&gt;. Here’s why a Systems Engineer treats their &amp;ldquo;home on the web&amp;rdquo; like a production environment.&lt;/p&gt;
&lt;h3 id="1-the-isolation-advantage"&gt;1. The Isolation Advantage&lt;/h3&gt;
&lt;p&gt;On shared hosting, you are at the mercy of your &amp;ldquo;neighbors.&amp;rdquo; If another site on the same IP gets hit with a DDoS or runs a malicious script, your site slows down or goes dark. On my VPS, my &lt;strong&gt;vCPU and RAM&lt;/strong&gt; are mine alone.&lt;/p&gt;</description></item></channel></rss>