Use the correct virtual hosts for production

Signed-off-by: Benoit Donneaux <benoit@leastauthority.com>

.gitea/workflows/jekyll.yaml

@@ -19,7 +19,6 @@ jobs:
       - name: Check out repository
         id: checkout
         uses: actions/checkout@v4
-        github-server-url: 'https://forge.of.tahoe-lafs.org/'
       - name: Change file ownership
         id: file_ownership
         run: |
@@ -47,9 +46,9 @@ jobs:
         id: build_site
         run: |
           # Overwrite the baseurl for preview only
-          if [ "${{ forge.event_name }}" = 'pull_request' ]; then
-            echo "Overwriting baseurl for pull_request ${{ forge.event.pull_request.number }}"
-            sed -i -r -e 's/^baseurl:\s*"([^"]*)"/baseurl: "\1\/${{ forge.event.pull_request.number }}"/' _config.yml
+          if [ "${{ gitea.event_name }}" = 'pull_request' ]; then
+            echo "Overwriting baseurl for pull_request ${{ gitea.event.pull_request.number }}"
+            sed -i -r -e 's/^baseurl:\s*"([^"]*)"/baseurl: "\1\/${{ gitea.event.pull_request.number }}"/' _config.yml
             grep "^baseurl:" _config.yml
           fi
           docker-compose run --rm -v "${JOB_CONTAINER_NAME}:/site" -w /site \
@@ -57,14 +56,14 @@ jobs:
       - name: Deploy Jekyll site
         id: deploy_site
         run: |
-          if [ "${{ forge.ref }}" = 'refs/heads/main' ]; then
+          if [ "${{ gitea.ref }}" = 'refs/heads/main' ]; then
             WEB_ROOT="${WEB_DIR}/live"
             WEB_VHOST="home.of.${WEB_DOMAIN}"
             WEB_CONTEXT='/'
           else
             WEB_ROOT="${WEB_DIR}/preview"
             WEB_VHOST="preview.of.${WEB_DOMAIN}"
-            WEB_CONTEXT='/${{ forge.event.pull_request.number }}/'
+            WEB_CONTEXT='/${{ gitea.event.pull_request.number }}/'
           fi
           # Save those variabes in the environment for the next steps
           echo "WEB_HOST=${WEB_HOST}" >> $GITHUB_ENV
@@ -79,7 +78,7 @@ jobs:
             ./_site/ "${WEB_USER}@${WEB_HOST}:${WEB_ROOT}${WEB_CONTEXT}"
       - name: Comment pull request
         id: comment_pull_request
-        if: ${{ always() && forge.event_name == 'pull_request' }}
+        if: ${{ always() && gitea.event_name == 'pull_request' }}
         uses: https://github.com/exercism/pr-commenter-action@v1.5.1
         with:
           template-variables: |
@@ -89,10 +88,10 @@ jobs:
               "deployOutcome": "${{ steps.deploy_site.outcome }}",
               "deployWebHost": "${{ env.WEB_VHOST }}",
               "deployWebContext": "${{ env.WEB_CONTEXT }}",
-              "gitActor": "${{ forge.actor }}",
-              "gitEventName": "${{ forge.event_name }}",
-              "gitWorkflow": "${{ forge.workflow }}",
-              "gitRunNumber": "${{ forge.run_number }}",
-              "gitRunAttempt": "${{ forge.run_attempt }}"
+              "gitActor": "${{ gitea.actor }}",
+              "gitEventName": "${{ gitea.event_name }}",
+              "gitWorkflow": "${{ gitea.workflow }}",
+              "gitRunNumber": "${{ gitea.run_number }}",
+              "gitRunAttempt": "${{ gitea.run_attempt }}"
             }
-          config-file: ".forgejo/pr-commenter.yml"
+          config-file: ".gitea/pr-commenter.yml"

.gitea/workflows/jekyll_cleanup.yml

@@ -7,14 +7,14 @@ on:
 
 env:
   WEB_HOST: webforge.of.tahoe-lafs.org
-  WEB_USER: bot-www
+  WEB_USER: www
   WEB_ROOT: /var/www/preview
-  WEB_CONTEXT: "/${{ forge.event.pull_request.number }}/"
+  WEB_CONTEXT: "/${{ gitea.event.pull_request.number }}/"
 jobs:
   jekyll_cleanup:
     runs-on: ubuntu-22.04
     permissions:
-      pull-requests: read
+      pull-requests: write
       actions: read
       contents: read
     steps:

src/_data/navigation.yml

@@ -10,4 +10,4 @@ main:
   - title: "About"
     url: "#about"
   - title: "Fork me"
-    url: "https://forge.of.tahoe-lafs.org/tahoe-lafs/web-landing-page/"
+    url: "https://code.lafs.eval.latfa.net/tahoe-lafs/web-landing-page/"

src/_posts/2022-10-03-release-v1.18.0.md

@@ -1,12 +1,14 @@
 ---
 layout: single
-title:  "v1.20.0 is released"
-date:   2024-12-19 05:48:54 +0000
-excerpt: "ANNOUNCING Tahoe, the Least-Authority File Store, v1.20.0"
+title:  "v1.18.0 is released"
+date:   2022-10-03 16:17:57 +0000
+excerpt: "ANNOUNCING Tahoe, the Least-Authority File Store, v1.18.0"
 header:
   teaser: /assets/images/posts/release.jpg
 ---
-The Tahoe-LAFS team is pleased to announce version 1.20.0 of
+ANNOUNCING Tahoe, the Least-Authority File Store, v1.18.0
+
+The Tahoe-LAFS team is pleased to announce version 1.18.0 of
 Tahoe-LAFS, an extremely reliable decentralized storage
 system. Get it with "pip install tahoe-lafs", or download a
 tarball here:
@@ -21,22 +23,15 @@ unique security and fault-tolerance properties:
 
   [https://tahoe-lafs.readthedocs.org/en/latest/about.html][about]
 
-The previous stable release of Tahoe-LAFS was v1.19.0, released on
-January 18, 2024. Major new features and changes in this release:
+The previous stable release of Tahoe-LAFS was v1.17.1, released on
+January 7, 2022.
 
-Declarative build system based on "hatch".
-The ability to creat mutable directories with a given private-key.
-
-Pulled in fixes from CBOR, stopped using the C version of CBOR and
-fixed incompatibilities with attrs and cryptography libraries.
-
-Besides all this there have been dozens of other bug-fixes and
-improvements.
-
-Enjoy!
+This release drops support for Python 2 and for Python 3.6 and earlier.
+twistd.pid is no longer used (in favour of one with pid + process creation time).
+A collection of minor bugs and issues were also fixed.
 
 [Read the full announcement][more]
 
 [download]: https://tahoe-lafs.org/downloads
 [about]: https://tahoe-lafs.readthedocs.org/en/latest/about.html
-[more]: https://lists.tahoe-lafs.org/pipermail/tahoe-dev/2024-December/010111.html
+[more]: https://lists.tahoe-lafs.org/pipermail/tahoe-dev/2022-October/010043.html

src/_posts/2024-05-29-new-landing-page.md

@@ -1,7 +1,7 @@
 ---
 layout: single
 title:  "New landing page"
-date:   2025-08-13 18:23:00 +0200
+date:   2024-05-29 21:47:57 +0200
 excerpt: "The old Tahoe-LAFS landing page is gone!"
 header:
   teaser: /assets/images/posts/old-landing-page-teaser.png
@@ -9,12 +9,14 @@ gallery:
   - image_path: /assets/images/posts/old-landing-page.png
     alt: "original"
 ---
-We're happy to announce that the migration from the [trac][old] landing page (see below) to the [jekyll][new] one has been completed.
+We're happy to announce that the migration of the [original][old] landing page to this one has been completed.
 
 Help us to contribute to it using this [repository][repo].
 
+Goodbye Trac...
+
 {% include gallery %}
 
 [old]: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/WikiStart
-[new]: https://home.of.tahoe-lafs.org/
-[repo]: https://forge.of.tahoe-lafs.org/tahoe-lafs/web-landing-page/
+[new]: https://www.lafs.eval.latfa.net/
+[repo]: https://code.lafs.eval.latfa.net/tahoe-lafs/web-landing-page/

src/index.html

@@ -55,8 +55,8 @@ contribute_list:
     alt: "issues"
     title: "Issues"
     excerpt: '<ul>
-      <li>Visit the <a href="https://tahoe-lafs.org/trac/tahoe-lafs"><b>issue</b></a> tracker</li>
-      <!--<li>Register an <a href="https://forge.of.tahoe-lafs.org/user/sign_up"><b>account</b></a> to interact</li>-->
+      <li>Visit the <a href="https://code.lafs.eval.latfa.net/tahoe-lafs/trac/issues"><b>issue</b></a> tracker</li>
+      <li>Register an <a href="https://code.lafs.eval.latfa.net/user/sign_up"><b>account</b></a> to interact</li>
     </ul>'
   - image_path: /assets/images/code.svg
     alt: "code"