apps: move knock and metadata out to their own repos, publish images to the Forgejo registry #292
Labels
No labels
audit-work
bug
docs
general-admin
major-upgrade
needs-vps-sync
new-service
on-hold
outside-work
post-podman
renovate
upstream
vps
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
mysticalsoap/docker#292
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
knock (
_helper/knock/, two long-running gunicorn services) and metadata (media/metadata/, five scripts plus beets on a daily Dagu job) are application code living in the infra repo asbuild:services. The infra repo should only consume images.Wanted: each moves to its own repo (or one shared apps repo) with CI on the existing Forgejo Actions runner that builds and publishes to the Forgejo container registry on release. This repo then references
git.mysticalsoap.com/mysticalsoap/<app>:<tag>@sha256:…as a plainimage:and Renovate bumps it like everything else. Config, secrets and the Dagu DAG stay here; only code and Dockerfile move.After this, config-renderer (#289 pinned it) is the only
build:left, kept as the one deliberate exception. dagu-tools is being replaced by the stock docker CLI image separately.