Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Selectable devcontainer config for multi-root workspace mono-repo #10020

Closed
red8888 opened this issue Jul 1, 2024 · 3 comments
Closed

Selectable devcontainer config for multi-root workspace mono-repo #10020

red8888 opened this issue Jul 1, 2024 · 3 comments
Assignees
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality

Comments

@red8888
Copy link

red8888 commented Jul 1, 2024

I'm not asking for full support like this: #1460

This is what I want to do:

monorepo/
  monorepo.code-workspace
  backend/
    .devcontainer/
      Dockerfile
      devcontainer.json
  frontend/
    .devcontainer/
      Dockerfile
      devcontainer.json

# in monorepo.code-workspace
{
    "folders": [
        {
            "name": "ROOT",
            "path": "."
        },
        {
            "name": "frontend",
            "path": "frontend"
        },
        {
            "name": "backend",
            "path": "backend"
        },
    ],
}

I want to view my subprojects with multi-root workspace and organize devcontainer configs under them like this- not have all dev container configs in some top level folder.

Then I just want to be able to select which dev container config to use and launch the whole workspace in that single container. I don't need a container for each workspace.

Is this possible? It seems like it should be but its demanding all my devcontainer configs live next to my workspace config.

I've resorted to opening each subfolder up as its own project but that totally breaks the git extension which can't find the .git folder.

@vscodenpa vscodenpa added the containers Issue in vscode-remote containers label Jul 1, 2024
@chrmarti chrmarti added the feature-request Request for new features or functionality label Dec 12, 2024
@vs-code-engineering vs-code-engineering bot added this to the Backlog Candidates milestone Dec 12, 2024
Copy link

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

Copy link

This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

Copy link

🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants