naming of services
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 8
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
should we have the same name for service type?
app-db, data-db, proxy, vs metabse, postgres:12, nginx.
pros:
simpler and more predictable basic structure.
cons:
if you want to use the same db for app-db and data-db, you can't reuse it. maybe it's not a bad thing
Contributor guide
No contributing guide indexed for this repository
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
The issue proposes standardizing service names such as app-db, data-db, proxy, metabase, postgres:12, and nginx, but names no files, tests, or entry points. First locate where service types are defined and used, then document the trade-off around reusing one database; done means the naming policy and its reuse behavior are decided.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100