GHCR keeps throttling the streamer's base image pull, so this stops publishing images from the GitHub mirror for now. Users build with docker compose up -d --build, which the README's setup already uses.
Removes .github/workflows/images.yml.
The docs no longer point at ghcr.io/branderson/:
the deployment guide says no images are published for now and keeps IMAGE_PREFIX for anyone who publishes their own;
the README drops its prebuilt-images pointer;
.env.example goes back to a placeholder registry;
the GitHub mirror doc and .dejima.md drop the GHCR and Actions notes.
The forge workflow is unchanged and keeps its retry from #17, for deployments that pull from the forge registry.
The GHCR packages already published under the GitHub account stay up, at whatever image was last built. They can be deleted from the account's package settings if they shouldn't linger. Actions stays enabled on the mirror, but with no workflows it does nothing.
Testing: prettier passes on the edited docs, shellcheck passes on mirror/github-mirror.sh, and nothing else refers to the GitHub workflow or ghcr.io/branderson.
**Summary generated by LLM agent**
GHCR keeps throttling the streamer's base image pull, so this stops publishing images from the GitHub mirror for now. Users build with `docker compose up -d --build`, which the README's setup already uses.
- Removes `.github/workflows/images.yml`.
- The docs no longer point at `ghcr.io/branderson/`:
- the deployment guide says no images are published for now and keeps `IMAGE_PREFIX` for anyone who publishes their own;
- the README drops its prebuilt-images pointer;
- `.env.example` goes back to a placeholder registry;
- the GitHub mirror doc and `.dejima.md` drop the GHCR and Actions notes.
- The forge workflow is unchanged and keeps its retry from #17, for deployments that pull from the forge registry.
The GHCR packages already published under the GitHub account stay up, at whatever image was last built. They can be deleted from the account's package settings if they shouldn't linger. Actions stays enabled on the mirror, but with no workflows it does nothing.
Testing: prettier passes on the edited docs, shellcheck passes on `mirror/github-mirror.sh`, and nothing else refers to the GitHub workflow or `ghcr.io/branderson`.
GHCR keeps throttling the streamer's base image pull, so drop the GitHub
image workflow for now and have users build with docker compose. The
forge workflow keeps its retry for the operator's own deployment.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary generated by LLM agent
GHCR keeps throttling the streamer's base image pull, so this stops publishing images from the GitHub mirror for now. Users build with
docker compose up -d --build, which the README's setup already uses..github/workflows/images.yml.ghcr.io/branderson/:IMAGE_PREFIXfor anyone who publishes their own;.env.examplegoes back to a placeholder registry;.dejima.mddrop the GHCR and Actions notes.The GHCR packages already published under the GitHub account stay up, at whatever image was last built. They can be deleted from the account's package settings if they shouldn't linger. Actions stays enabled on the mirror, but with no workflows it does nothing.
Testing: prettier passes on the edited docs, shellcheck passes on
mirror/github-mirror.sh, and nothing else refers to the GitHub workflow orghcr.io/branderson.Pull request closed