Background
Previous work for localhost subdomains in ShareThrift involved hardcoding port assignments for applications. The npm package portless and its source code (vercel-labs/portless) enable dynamic port routing and custom subdomain management for local development, potentially simplifying and improving this workflow.
Acceptance Criteria
- Investigate and document how portless can replace current hardcoded port handling for localhost subdomains across ShareThrift applications.
- Prototype dynamic port management using portless in place of static config in at least one part of the dev stack.
- Summarize benefits, challenges, caveats, and migration considerations for moving to portless from the current pattern.
- Create an ADR (Architecture Decision Record) in the repository to capture all findings, decision rationale, and a clear recommendation for or against adopting portless. Link to this ADR from this issue.
Resources
Notes
- If portless is not a viable solution, document the reason, alternatives considered, and recommendations for next steps.
Background
Previous work for localhost subdomains in ShareThrift involved hardcoding port assignments for applications. The npm package portless and its source code (vercel-labs/portless) enable dynamic port routing and custom subdomain management for local development, potentially simplifying and improving this workflow.
Acceptance Criteria
Resources
Notes