bringing new Medley release online

[Nick Briggs]

These are the instructions from online/docs/OIO_Operations_Guide.md -- interlined are my comments

## Bring new Medley release online

1. Make sure that the Docker image corresponding to the new Medley release has been created and uploaded to 

Docker Hub under interlisp/medley.

What's the URL at which you do this? I'm guessing https://hub.docker.com/r/interlisp/medley/tags 

The most recent tag is 260521-db8a7f4a_260319-9259716e (this looks like a Medley tag "_" a Maiko tag), and the "latest" tag has the same digest.

  When listing the Tags (sorted by Newest) under interlisp/medley, there should be

a tag whose first "part" (up to the first underscore) corresponds to the release tag for the new Medley release.

This will usually be the second tag listed immediately after the "latest" tag.  If no matching tag can be found,

then you will have to back and run the `Build/Push Docker Image` action in the Medley repo on Github.

At Interlisp/medley/actions we have

.github/workflows/buildDocker.yml

Build/Push Medley Release

Build/Push Release, Docker, OIO

Copilot code review

Run HCFILES

Which one of these replaced "Build/Push Docker Image"? Does "Build/Push Release, Docker, OIO" also do the item below?

I ran both "Build/Push Medley Release" and "Build/Push Release, Docker, OIO"

2.  In the interlisp/online Github repo, run the `Build/Push Online-Medley Docker Image` action.

I ran this action.

  This will create an

online Docker image for the new Medley release and store it in the Github Container Repository tagged as 

`ghcr.io/interlisp/online-medley:development`.

If I look at https://ghcr.io/interlisp/online-medley:development that redirects to https://github.com/interlisp/online/pkgs/container/online-medley  and the "Latest" tag there is

251214-9ae1f130_260521-db8a7f4a_260319-9259716e

OK, that has a piece of the tag with the expected dates for Medley/Maiko, 

3.  Test this new online-Medley image as follows:

    3.1 Connect via ssh to the online.interlisp.org host as described in Section 2 above. 

    3.2  Execute: `oio medley pulldev`

Did this, it reports:

ubuntu@oio:~$ oio medley pulldev

development: Pulling from interlisp/online-medley

Digest: sha256:0e0ae23af12357e4022f07cd55bde8e94304e200fb33f934ad667a820db8bc6f

Status: Image is up to date for ghcr.io/interlisp/online-medley:development

ghcr.io/interlisp/online-medley:development

Untagged: ghcr.io/interlisp/online-medley:2bdeleted

Latest Online-medley development release pulled from Github Container Registry

Not sure if I can get the sha256 digest that this should match up with -- at https://hub.docker.com/layers/interlisp/medley/260521-db8a7f4a_260319-9259716e/images/sha256-0ab7b665de1824aa5128da540e6553f08067310911dfb1a76ae24cc1f91750c8 that digest doesn't match (it's the manifest digest), and the index digest that's presented there is sha256:d25166... which doesn't match the above either.

    3.3  From a web browser go to `https://online.interlisp.org:8081` to connect to the development version

         of Interlisp Online.  Login (or login as guest) and Run Medley.  The Medley that starts should be the new

         Medley release.  Run it through its paces to make it works.  Then logout of Medley.

The Medley that it starts up has a MAKESYSDATE of 18-Mar-2026 02:35:08 -- so it is NOT the newly released one.

Where did this all go wrong?

4.  Retag new online-Medley image from :development to :production

    4.1   Connect via ssh to the online.interlisp.org host as described in Section 2 above.

    4.2   Execute: `oio medley dev2prod`

    4.3  Next time you `Run Medley` at `https://online.interlisp.org`, you should get the new Medley release.

I didn't do this, since dev isn't what it should be.

-- Nick