Repository navigation
fix(deploy): fully qualified image names for podman; dormant projects on the intake card - #61
Merged
Merged
Conversation
…ects apart on the intake card The compose stack was brought up on rootless podman for the first time: short image names (python, node, nginx, postgres) do not resolve without a configured registry. The ingestion card now lists projects silent for over 7 days on one line. Security notes record what was verified.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
backend/Containerfile,dashboard/Containerfile,docker-compose.yml,podman-compose.yml: image names are fully qualified (docker.io/library/...). Found by bringing the stack up for real on rootless podman 5.7: the build failed with "short-name did not resolve".splitDormantwith a test.docs/security.md: what was verified;docs/roadmap.md: decision that reply text stays out (metadata only).Verified
podman-compose up --buildwith a password: PostgreSQL migrated to head (6 revisions), backend/health200, dashboard proxy 200, only 127.0.0.1 listeners, PostgreSQL unpublished. WithoutPOSTGRES_PASSWORDit refuses to start. Test stack removed afterwards.pip-audit(backend): no known vulnerabilities.npm audit --omit=dev: 0.tscclean, 45 tests pass, vite build OK.