Update external docs

Author: garrett

external/bots/README.md

@@ -49,9 +49,9 @@ For running and debugging the images:
 ## Image location
 
 Downloaded images are stored into ~/.cache/cockpit-images/ by default. If you
-want to change that, you can set the `cockpit.bots.images-data-dir` variable
-with `git config` to a directory where to store the pristine virtual machine
-images.  For example:
+want to change that, you can set `$COCKPIT_IMAGES_DATA_DIR` or the
+`cockpit.bots.images-data-dir` variable with `git config` to a directory where
+to store the pristine virtual machine images.  For example:
 
     git config cockpit.bots.images-data-dir /srv/cockpit/images
 

external/source/HACKING.md

@@ -20,7 +20,7 @@ remote, for example with
 
 ## Setting up development container
 
-The cockpit team maintains a [cockpit/tasks container](https://quay.io/repository/cockpit/tasks)
+The cockpit team maintains a [cockpit/tasks container](https://ghcr.io/cockpit-project/tasks)
 for both local development and CI. If you can install [toolbx](https://containertoolbx.org/) or
 [distrobox](https://distrobox.privatedns.org/) on your system, it is highly
 recommended to do that:
@@ -41,7 +41,7 @@ recommended to do that:
 
 2. Create a development toolbox for Cockpit
 
-       toolbox create --image quay.io/cockpit/tasks -c cockpit
+       toolbox create --image ghcr.io/cockpit-project/tasks -c cockpit
 
 3. Enter the toolbox:
 
@@ -55,7 +55,7 @@ toolbox container. If desired, you can install additional packages with
 The Cockpit team occasionally refreshes the `tasks` container image.
 To re-create your development container from the latest image, run:
 
-    podman pull quay.io/cockpit/tasks
+    podman pull ghcr.io/cockpit-project/tasks
     toolbox rm cockpit
 
 ...and then repeat steps 2 and 3 from above.

external/source/test/README.md

@@ -25,7 +25,7 @@ You first need to build cockpit, and install it into a VM:
 
     test/image-prepare
 
-This uses the default OS image, which is currently Fedora 38. See `$TEST_OS`
+This uses the default OS image, which is currently Fedora 39. See `$TEST_OS`
 below how to select a different one.
 
 In most cases you want to run an individual test in a suite, for example:
@@ -98,7 +98,7 @@ Pixel tests make a screenshot of a selector and compare it to a known good
 reference image. if there is a difference, the test fails and a pixel
 difference is shown.
 
-This works as our tests run in the [cockpit/tasks container](https://quay.io/repository/cockpit/tasks)
+This works as our tests run in the [cockpit/tasks container](https://ghcr.io/cockpit-project/tasks)
 which pins the browser and font rendering so repeated runs provide the same
 pixels. To generate new pixels, this tasks container must be used; your own
 browser and font rendering software might generate different results. For more
@@ -158,16 +158,13 @@ to push pixel tests.
 You can set these environment variables to configure the test suite:
 
     TEST_OS    The OS to run the tests in.  Currently supported values:
-                  "centos-8-stream"
+                  "centos-9-stream"
                   "debian-stable"
                   "debian-testing"
-                  "fedora-38"
                   "fedora-39"
+                  "fedora-40"
                   "fedora-coreos"
-                  "fedora-testing"
-                  "rhel-8-10"
-                  "rhel-8-10-distropkg"
-                  "rhel-9-3"
+                  "rhel-9-4"
                   "rhel4edge",
                   "ubuntu-2204"
                   "ubuntu-stable"