deep-foundation / deep-foundation/deeplinks
using public networking
Open
invalid
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Somehere env uses host.docker.internal for linking to some services. Maybe we should change links to currnet domain in docker network, and dont use public network to networking inside services
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the environment configuration that uses host.docker.internal and trace how services are linked in the Docker network; done means service-to-service links use the current Docker-network domain without relying on public networking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100