kenmirrors/ente
1
0
Fork 0
mirror of https://github.com/ente-io/ente.git synced 2025-07-28 12:48:19 +00:00
Code Issues Packages Projects Releases Wiki Activity
ente/server/docs/publish.md
Manav Rathi 182fd89356
[server] Retain published image commit as branch instead of tag 
Overwriting tags is clunky (besides being generally discouraged). e.g. pulling
the overwritten tags locally requires `git fetch --force --tags`. So instead use
the branch `server/ghcr` to point to the commit from which the latest published
ghcr docker image has been built
2024-12-30 13:58:08 +05:30

1.9 KiB
Raw Blame History

Publishing images

There are two different images we publish - internal and external.

Internal

The internal images can be built and run by triggering the "Server (release)" workflow. You can trigger it either from GitHub's UI on the Actions tab, or use the following command:

gh workflow run server-release.yml

This will take the latest main, package it into a Docker image, and publish it to our Scaleway registry. From there, we can update our production instances to use this new image (see deploy/README).

External

Periodically, we can republish a new image from an existing known-to-be-good commit to the GitHub Container Registry (GHCR) so that it can be used by folks without needing to clone our repository just for building an image. For more details about the use case, see docker.md.

To publish such an external image, firstly find the commit of the currently running production instance.

curl -s https://api.ente.io/ping | jq -r '.id'

We can publish from any arbitrary commit really, but by using the commit that's already seen production for a few days, we avoid externally publishing images with issues.

Then, trigger the "Publish (server)" workflow, providing it the commit. You can trigger it either from GitHub's UI or using the gh cli. With the CLI, we can combine both these steps too.

gh workflow run server-publish.yml -F commit=`curl -s https://api.ente.io/ping | jq -r '.id'`

Once the workflow completes, the resultant image will be available at ghcr.io/ente-io/server. The image will be tagged by the commit SHA. The latest image will also be tagged, well, "latest".

The workflow will also update the branch server/ghcr to point to the commit it used to build the image. This branch will be overwritten on each publish, and thus it server/ghcr points to the code from which the most recent ghcr docker image for museum has been built.