Confusing domain setting for service with Docker Compose
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
When user creates a service using Docker Compose, they need to declaratively configure domains in docker-compose.yaml. However, the admin console also has a Domain tab that might make users think they can configure the domain settings through the tab (but it's not).
Describe the solution you'd like
The domain tab in the console should show no "add domain" button in it. Also it would be nice if it has a link to the corresponding document.
Describe alternatives you've considered
Nice to have: The tab parses the yaml file provided by a user and displays the domain configuration (read-only) in it.
Additional context
No response
Will you send a PR to implement it?
Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the admin console's Domain tab and the Docker Compose domain documentation. Verify that the tab no longer offers an "add domain" action and that it links to the corresponding document; the optional YAML parsing display is described as a nice-to-have.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, typescript
- Domain
- devops, frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100