[codex] Align media services with live routing - #90
Draft
ironicbadger wants to merge 1 commit into
Draft
Conversation
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
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.
Summary
This PR aligns the media service routing/configuration with the live infrastructure state.
Changes include:
*.demo.ktz.meCaddy wildcard endpoint for the Jellyfin demo route.Why
These changes were split out from the local LLM/Hermes branch because they are actual infra/media routing fixes and should be reviewed independently from the Framework LLM work.
Impact
Validation
git diff --check main..HEADansible-playbook --syntax-check run.yamlansible-inventory --graphmainand touches only the expected media/routing files.Known warning: Ansible still reports the existing
ktz-cloudgroup/host name warning; this PR does not introduce it.