Proposal: Add `devcontainers init` command similar to `devcontainerize`
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, typescript
- Domain
- cli, developer-experience
Research direction
Start by reviewing the existing CLI structure and comparing it with the devcontainerize tool and the devcontainers/images repository. Done means an official devcontainers init command detects the project type, fetches the appropriate Dockerfile and devcontainer.json, creates .devcontainer, and optionally updates .gitignore in a Git repository.
Written by the indexing model from the issue text.
Description
Hello devcontainers team,
I've recently created a tool called devcontainerize (https://www.npmjs.com/package/devcontainerize, https://github.com/mathdroid/devcontainerize) that automatically detects a project's type and sets up the appropriate devcontainer configuration.
The tool:
- Detects the project type based on files in the current directory.
- Fetches appropriate Dockerfile and devcontainer.json from the devcontainers/images repository.
- Creates a .devcontainer directory with these files.
- Optionally adds .devcontainer to .gitignore if in a Git repository.
I believe a similar functionality could be valuable as part of the official devcontainers CLI, potentially as a devcontainers init command.
I'm keen to contribute this functionality to the official CLI if the team is interested. This could help streamline the process of setting up devcontainers for various project types and improve the overall developer experience.
Would you be open to discussing this further? I'd be happy to provide more details about the implementation or discuss how we could adapt it to fit within the existing CLI structure.
- 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
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vicharanashala/fln#563 ·