Custom devcontainer folder name when developing features locally
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli
Research direction
Start by tracing the CLI's --config handling and the code that resolves locally referenced features. Check how the current .devcontainer requirement is enforced and whether related tests cover arbitrary config locations. Done means a locally referenced feature works from an arbitrary folder without requiring the .devcontainer name.
Written by the indexing model from the issue text.
Description
I am exploring the idea of using a devcontainer as a portable toolbox. The main idea is to have a repo that just constitutes what would be the usual .devcontainer folder. The problem is that I do not want to use that name, to not clash with that name if the project I use it within is already using devcontainers.
The idea is that through locally developed features, I could create a number of scripts (e.g., local uv tools) that I can just use within any project (and benefit of the ease of mounting of devcontainers).
All works really well, and I am happy where this is going, but the main problem is that to reference a feature that lives locally, I must have a .devcontainer folder. For the rest, I can call the folder whatever I want and just pass a --config flag.
Is there any chance where that constraint is removed and locally referenced features work in any arbitrary folder? Maybe the parent folder of where --config is pointing to?
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 461
- Avg merge
- 18m
- Merged PRs (30d)
- 5
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.
More from devcontainers/cli
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
devcontainers/cli#1203 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
devcontainers/cli#1178 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
devcontainers/cli#1308 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 78/100
devcontainers/cli#1307 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
devcontainers/cli#1305 ·
All issues in devcontainers/cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·