fix(infra): compatibilizar resolução de porta com Render e Docker#16
Merged
Conversation
Extrai logica de parsing de env para src/infra/http/env.ts com funcao resolverEnv que prioriza PORT (injetado pelo Render/cloud) sobre PORTA (variavel local/Docker), mantendo o default 3000 quando nenhuma e definida. Adiciona 10 testes unitarios cobrindo resolucao de porta e validacao das variaveis obrigatorias (JWT_SECRETO, MONGO_URI, REDIS_URL).
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.
Summary
servidor.tsintosrc/infra/http/env.ts, exposingresolverEnvas a testable functionresolverEnvprioritizesPORT(injected by Render/cloud platforms) overPORTA(local/Docker convention), keeping default3000when neither is set3000while Render injectedPORT=10000, causing health checks to fail and the service to crash on startupRoot cause
Render injects the
PORTenvironment variable automatically. The app was only readingPORTA(Portuguese naming convention), soschemaEnv.safeParse(process.env)fell back to the default3000— mismatching Render's expected port.Test plan
src/testes/unitarios/infra/env.test.tsPORTtakes precedence overPORTAwhen both are setPORTalone resolves correctly (Render scenario)PORTAalone resolves correctly (local/Docker scenario)3000applies when neither is setJWT_SECRETO, missingMONGO_URI, missingREDIS_URLpnpm lint && pnpm typecheck && pnpm test— all passing locally🤖 Generated with Claude Code