From b21831536e53aeba837a361d805b126f75a1f317 Mon Sep 17 00:00:00 2001 From: andrzej Date: Fri, 15 Nov 2024 16:26:17 +0100 Subject: [PATCH] edits --- content/posts/permissions-strike-again.md | 6 +++--- public/css/main.css | 4 ++-- public/index.xml | 2 +- public/posts/index.html | 2 +- public/posts/index.xml | 2 +- public/posts/permissions-strike-again/index.html | 8 ++++---- public/tags/linux/index.html | 2 +- public/tags/linux/index.xml | 2 +- themes/cuqui/assets/css/main.css | 4 ++-- 9 files changed, 16 insertions(+), 16 deletions(-) diff --git a/content/posts/permissions-strike-again.md b/content/posts/permissions-strike-again.md index 2d72eac..0a625e0 100644 --- a/content/posts/permissions-strike-again.md +++ b/content/posts/permissions-strike-again.md @@ -1,7 +1,7 @@ +++ date = '2024-11-13T11:53:13+01:00' draft = false -title = 'Permissions Strike Again' +title = 'Permissions strike again' tags = ['linux'] +++ @@ -15,9 +15,9 @@ Please, Andrzej. Please. The next time you're building a website, be it for a cl ## What? -In Linux we open directories by 'executing' them. A directory is an executable that lists part of file-system for us, basically. Now, by default, the home directory is only executable by its owner. This makes sense when you think about it -- you don't want your sister, or co-worker, or (more likely) whatever barely-audited application you're installing today, to be able to open that directory. But you probably do want your webserver to be able to open it, especially if you are symlinking to it from `/var/www`. +In Linux we open directories by 'executing' them. A directory is an executable that maps part of the file-system for us. Now, by default, the home directory is only executable by its owner. This makes sense when you think about it -- you don't want your sister, or co-worker, or (more likely) whatever barely-audited application you're installing today, to be able to open that directory. But you probably *do* want your webserver to be able to open it, especially if you are symlinking to it from `/var/www` or wherever. -[Hugo](https://gohugo.io/) (the framework I'm using to build this blog) likes to deploy to the home directory by default. In fact there are lots of reasons why you'd want to deploy there. I do this exact same thing with [Jenkins](https://jenkins.io), and I wasted an hour troubleshooting this exact same problem when I set up that server too. +There are lots of reasons why you'd want to deploy to the home directory of an unprivileged user. I do this exact same thing with [Jenkins](https://jenkins.io), and I wasted an hour troubleshooting this exact same problem when I set up that server too. So, Andrzej of the future (did anyone non-ghoulish win an election yet?), for future reference, let's say you're deploying to `/home/devlog/website`: diff --git a/public/css/main.css b/public/css/main.css index 91d28a7..796eaa9 100644 --- a/public/css/main.css +++ b/public/css/main.css @@ -139,8 +139,8 @@ a:hover { h1 { color: var(--rp-text); - background-color: var(--rp-highlight-high); - /* background-image: linear-gradient(to bottom, var(--rp-highlight-high), var(--rp-overlay), var(--rp-base)); */ + /* background-color: var(--rp-highlight-high); */ + background-image: linear-gradient(to bottom, var(--rp-highlight-high) 80%, var(--rp-base)); border-radius: 1rem 1rem 0 0; padding: 1rem; text-shadow: 1px 1px 5px var(--rp-base); diff --git a/public/index.xml b/public/index.xml index a9024a4..32e1b3f 100644 --- a/public/index.xml +++ b/public/index.xml @@ -16,7 +16,7 @@ <p><strong>I had a bit of an issue with my <a href="https://demos.ajstepien.xyz">website</a> recently.</strong></p> <p>I pushed some changes incorporating images for the first time (I know &ndash; very swish, very modern), and everything seemed to be working just fine, but when I loaded the production site in Firefox&hellip; the images were not styled. Stranger still, they <em>were</em> styled when I loaded the same page in Chrome.</p> <p>The experienced computer touchers amongst you will be saying &ldquo;this is obviously a cache problem&rdquo;, and you&rsquo;re right, it is obviously a cache problem. Pressing <code>CTR + SHIFT + R</code> (which forces Firefox to clear the cache and do a full reload) proved this thesis, and solved the immediate problem for me, on my machine. But what about other people&rsquo;s machines? <strong>I needed to cache-bust.</strong></p> - Permissions Strike Again + Permissions strike again http://localhost:1313/posts/permissions-strike-again/ Wed, 13 Nov 2024 11:53:13 +0100 http://localhost:1313/posts/permissions-strike-again/ diff --git a/public/posts/index.html b/public/posts/index.html index 31df453..907a91b 100644 --- a/public/posts/index.html +++ b/public/posts/index.html @@ -65,7 +65,7 @@
  • -

    Permissions Strike Again

    +

    Permissions strike again

    Configuring Apache really isn’t rocket science. There are a wealth of great tutorials online, the documentation is very well documented, and the defaults work more or less out of the box. But it’s one of those jobs that I do just infrequently enough that I always forget things in the interim, and end up making the same old mistakes.

    And it almost always has to do with permissions.

    So, I’m writing this post both as a means of christening this devlog (Hi! I’m Andrzej! Hire me!) and also as a reminder to myself that the home folder is not executable by default.

    diff --git a/public/posts/index.xml b/public/posts/index.xml index 51213e4..a082242 100644 --- a/public/posts/index.xml +++ b/public/posts/index.xml @@ -16,7 +16,7 @@ <p><strong>I had a bit of an issue with my <a href="https://demos.ajstepien.xyz">website</a> recently.</strong></p> <p>I pushed some changes incorporating images for the first time (I know &ndash; very swish, very modern), and everything seemed to be working just fine, but when I loaded the production site in Firefox&hellip; the images were not styled. Stranger still, they <em>were</em> styled when I loaded the same page in Chrome.</p> <p>The experienced computer touchers amongst you will be saying &ldquo;this is obviously a cache problem&rdquo;, and you&rsquo;re right, it is obviously a cache problem. Pressing <code>CTR + SHIFT + R</code> (which forces Firefox to clear the cache and do a full reload) proved this thesis, and solved the immediate problem for me, on my machine. But what about other people&rsquo;s machines? <strong>I needed to cache-bust.</strong></p> - Permissions Strike Again + Permissions strike again http://localhost:1313/posts/permissions-strike-again/ Wed, 13 Nov 2024 11:53:13 +0100 http://localhost:1313/posts/permissions-strike-again/ diff --git a/public/posts/permissions-strike-again/index.html b/public/posts/permissions-strike-again/index.html index 9247956..6353207 100644 --- a/public/posts/permissions-strike-again/index.html +++ b/public/posts/permissions-strike-again/index.html @@ -4,7 +4,7 @@ - Permissions Strike Again | Coding with Andrzej + Permissions strike again | Coding with Andrzej @@ -50,7 +50,7 @@
    -

    Permissions Strike Again

    +

    Permissions strike again

    @@ -59,8 +59,8 @@

    So, I’m writing this post both as a means of christening this devlog (Hi! I’m Andrzej! Hire me!) and also as a reminder to myself that the home folder is not executable by default.

    Please, Andrzej. Please. The next time you’re building a website, be it for a client or for yourself, and you find yourself scratching your head, wondering what error you may have made in the .confs, checking the permissions of your symlink again and again, ask yourself: is my symlink pointing to a directory in the home folder? Because Apache can’t open the home folder until you change the permissions!

    What?

    -

    In Linux we open directories by ’executing’ them. A directory is an executable that lists part of file-system for us, basically. Now, by default, the home directory is only executable by its owner. This makes sense when you think about it – you don’t want your sister, or co-worker, or (more likely) whatever barely-audited application you’re installing today, to be able to open that directory. But you probably do want your webserver to be able to open it, especially if you are symlinking to it from /var/www.

    -

    Hugo (the framework I’m using to build this blog) likes to deploy to the home directory by default. In fact there are lots of reasons why you’d want to deploy there. I do this exact same thing with Jenkins, and I wasted an hour troubleshooting this exact same problem when I set up that server too.

    +

    In Linux we open directories by ’executing’ them. A directory is an executable that maps part of the file-system for us. Now, by default, the home directory is only executable by its owner. This makes sense when you think about it – you don’t want your sister, or co-worker, or (more likely) whatever barely-audited application you’re installing today, to be able to open that directory. But you probably do want your webserver to be able to open it, especially if you are symlinking to it from /var/www or wherever.

    +

    There are lots of reasons why you’d want to deploy to the home directory of an unprivileged user. I do this exact same thing with Jenkins, and I wasted an hour troubleshooting this exact same problem when I set up that server too.

    So, Andrzej of the future (did anyone non-ghoulish win an election yet?), for future reference, let’s say you’re deploying to /home/devlog/website:

    1. Add Apache to the ‘devlog’ user group.
      2. diff --git a/public/tags/linux/index.html b/public/tags/linux/index.html index 30d7038..9c5be0e 100644 --- a/public/tags/linux/index.html +++ b/public/tags/linux/index.html @@ -65,7 +65,7 @@
    2. -

      Permissions Strike Again

      +

      Permissions strike again

      Configuring Apache really isn’t rocket science. There are a wealth of great tutorials online, the documentation is very well documented, and the defaults work more or less out of the box. But it’s one of those jobs that I do just infrequently enough that I always forget things in the interim, and end up making the same old mistakes.

      And it almost always has to do with permissions.

      So, I’m writing this post both as a means of christening this devlog (Hi! I’m Andrzej! Hire me!) and also as a reminder to myself that the home folder is not executable by default.

      diff --git a/public/tags/linux/index.xml b/public/tags/linux/index.xml index 683033f..1458939 100644 --- a/public/tags/linux/index.xml +++ b/public/tags/linux/index.xml @@ -16,7 +16,7 @@ <p><strong>I had a bit of an issue with my <a href="https://demos.ajstepien.xyz">website</a> recently.</strong></p> <p>I pushed some changes incorporating images for the first time (I know &ndash; very swish, very modern), and everything seemed to be working just fine, but when I loaded the production site in Firefox&hellip; the images were not styled. Stranger still, they <em>were</em> styled when I loaded the same page in Chrome.</p> <p>The experienced computer touchers amongst you will be saying &ldquo;this is obviously a cache problem&rdquo;, and you&rsquo;re right, it is obviously a cache problem. Pressing <code>CTR + SHIFT + R</code> (which forces Firefox to clear the cache and do a full reload) proved this thesis, and solved the immediate problem for me, on my machine. But what about other people&rsquo;s machines? <strong>I needed to cache-bust.</strong></p> - Permissions Strike Again + Permissions strike again http://localhost:1313/posts/permissions-strike-again/ Wed, 13 Nov 2024 11:53:13 +0100 http://localhost:1313/posts/permissions-strike-again/ diff --git a/themes/cuqui/assets/css/main.css b/themes/cuqui/assets/css/main.css index 91d28a7..796eaa9 100644 --- a/themes/cuqui/assets/css/main.css +++ b/themes/cuqui/assets/css/main.css @@ -139,8 +139,8 @@ a:hover { h1 { color: var(--rp-text); - background-color: var(--rp-highlight-high); - /* background-image: linear-gradient(to bottom, var(--rp-highlight-high), var(--rp-overlay), var(--rp-base)); */ + /* background-color: var(--rp-highlight-high); */ + background-image: linear-gradient(to bottom, var(--rp-highlight-high) 80%, var(--rp-base)); border-radius: 1rem 1rem 0 0; padding: 1rem; text-shadow: 1px 1px 5px var(--rp-base);