pages.sr.ht-examples: Update stale eleventy example v1 SUPERSEDED

I saw a [post on the mailing list][1] where a user had some trouble
using the Debian + Eleventy example due to it referencing an old
version of Debian that is no longer supported by builds.st.ht.

This patchset improves the example in several ways:

  - Image changed from stale debian/buster to evergreen debian/stable
  - Node.js version updated to new LTS and a non-distro-specific repo
  - Updated env var to disable the npm progress bar

[1]: https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3CCAPxX4hCqQFqymCCdOy70gEiwQojAALO7iVjPujybp0433QZ3TA%40mail.gmail.com%3E

Noelle Leigh (3):
  eleventy.yml: Switch to debian/stable
  eleventy.yml: Switch to distroless nodesource, v20
  eleventy.yml: Disable progress bar correctly

 eleventy.yml | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

--
2.30.2

Is the third-party repository actually necessary? Current Debian stable 
ships with Node 18 and NPM 9 which is well within Eleventy's required 
Node 14 or newer.

Taavi

Noelle Leigh <noelle_leigh@fastmail.com>

1 year, 4 months ago

Technically it's not necessary, but it does provide a helpful example
for how to install a newer version from a third-party repo, which is not
intuitive for users who are unfamiliar with gpg.

[PATCH pages.sr.ht-examples 1/3] eleventy.yml: Switch to debian/stable Export this patch

Won't eventually fall off the support list
---
 eleventy.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/eleventy.yml b/eleventy.yml
index c74b315..7b1dd58 100644
--- a/eleventy.yml
+++ b/eleventy.yml
@@ -1,5 +1,5 @@
 # Eleventy: https://www.11ty.dev/
-image: debian/buster
+image: debian/stable
 packages:
   - nodejs
 repositories:
-- 
2.30.2

[PATCH pages.sr.ht-examples 2/3] eleventy.yml: Switch to distroless nodesource, v20 Export this patch

This way the distro doesn't need to be specified twice. v20 is the
current LTS release of Node.js.

The new key-id was obtained using:

  $ curl -s https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg -n -v --import
  gpg: pub  rsa2048/2F59B5F99B1BE0B4 2016-05-23  NSolid <nsolid-gpg@nodesource.com>
  gpg: Total number processed: 1
---
 eleventy.yml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/eleventy.yml b/eleventy.yml
index 7b1dd58..99ac07b 100644
--- a/eleventy.yml
+++ b/eleventy.yml
@@ -3,10 +3,10 @@ image: debian/stable
 packages:
   - nodejs
 repositories:
-  # https://github.com/nodesource/distributions/blob/master/README.md#debmanual
+  # https://github.com/nodesource/distributions/blob/master/README.md#debian-and-ubuntu-based-distributions
   nodesource.com: >-
-    https://deb.nodesource.com/node_14.x buster main
-    9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280
+    https://deb.nodesource.com/node_20.x nodistro main
+    2F59B5F99B1BE0B4
 oauth: pages.sr.ht/PAGES:RW
 environment:
   site: example.org
-- 
2.30.2

Taavi Väänänen <hi@taavi.wtf>

1 year, 4 months ago

Is the third-party repository actually necessary? Current Debian stable 
ships with Node 18 and NPM 9 which is well within Eleventy's required 
Node 14 or newer.

Taavi

[PATCH pages.sr.ht-examples 3/3] eleventy.yml: Disable progress bar correctly Export this patch

Changed for newer versions of npm.
---
 eleventy.yml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/eleventy.yml b/eleventy.yml
index 99ac07b..4e88172 100644
--- a/eleventy.yml
+++ b/eleventy.yml
@@ -10,8 +10,9 @@ repositories:
 oauth: pages.sr.ht/PAGES:RW
 environment:
   site: example.org
-  # https://docs.npmjs.com/cli/v6/using-npm/config#progress
-  CI: "TRUE"
+  # Disable npm progress bar
+  # https://docs.npmjs.com/cli/v10/using-npm/config#progress
+  npm_config_progress: "false"
 tasks:
 - install: |
     cd $site
-- 
2.30.2