<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Webserver on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/webserver/</link>
    <description>Recent content in Webserver on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 11:21:02 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/webserver/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using ACLs to give a group write access to /var/www/html without changing ownership</title>
      <link>https://linuxeries.org/post/2026-10-10-using-acls-to-give-a-group-write-access-to-va/</link>
      <pubDate>Sat, 10 Oct 2026 11:21:02 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-10-10-using-acls-to-give-a-group-write-access-to-va/</guid>
      <description>&lt;h2 id=&#34;why-acls-instead-of-changing-ownership&#34;&gt;Why ACLs instead of changing ownership?&lt;/h2&gt;&#xA;&lt;p&gt;When a web server runs as &lt;code&gt;www-data&lt;/code&gt; and the dev squad needs to touch files in &lt;code&gt;/var/www/html&lt;/code&gt;, the quick fix is usually &lt;code&gt;chgrp&lt;/code&gt; the directory and slap a write bit on the group. That swaps the group ownership, which can trip up services that expect the original group or automated deploy scripts that hard‑code the owner. ACLs let you hand out the right permissions without touching the classic ownership columns.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
