Regenerate docker-compose.yaml to fix 502 on /docs - #670
Merged
Conversation
The docker-compose.yaml mirror was stale relative to AppHost.cs: it was
missing the scalar-docs container and the frontend's NUXT_SCALAR_DOCS_URL
env var, so /docs 502'd in real docker-compose deployments even though it
worked fine under the Aspire dev host.
Regenerated via `aspire publish` (the aspire CLI, not `dotnet run
--publisher docker-compose`, which still hits the long-standing "Sequence
contains more than one matching element" bug). As a side effect, each
backend service's internal HTTP_PORTS/expose now hardcodes 8080 instead of
interpolating ${SERVICES_X_PORT} from .env — harmless since each service
only listens inside its own container network namespace.
.env is intentionally left untouched: regenerating it would have blanked
out the checked-in default parameter values (postgres/tranga/en/false) and
dropped MangaDirectory/PUID/PGID entirely, since those aren't Aspire
parameters and only exist in .env via manual curation.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Pd8xypZRnjVyrJNLbxiXVB
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.
The docker-compose.yaml mirror was stale relative to AppHost.cs: it was missing the scalar-docs container and the frontend's NUXT_SCALAR_DOCS_URL env var, so /docs 502'd in real docker-compose deployments even though it worked fine under the Aspire dev host.
Regenerated via
aspire publish(the aspire CLI, notdotnet run --publisher docker-compose, which still hits the long-standing "Sequence contains more than one matching element" bug). As a side effect, each backend service's internal HTTP_PORTS/expose now hardcodes 8080 instead of interpolating ${SERVICES_X_PORT} from .env — harmless since each service only listens inside its own container network namespace..env is intentionally left untouched: regenerating it would have blanked out the checked-in default parameter values (postgres/tranga/en/false) and dropped MangaDirectory/PUID/PGID entirely, since those aren't Aspire parameters and only exist in .env via manual curation.
Claude-Session: https://claude.ai/code/session_01Pd8xypZRnjVyrJNLbxiXVB