Skip to content

Conversation

@chheis
Copy link

@chheis chheis commented Dec 23, 2025

I added a devcontainer configuration to setup a fast and easy environment.
But, with reusing the setup scripts the interactive input is still mandatory.
So did not work out yet.
Maybe in a collaborative cooperation we can fix it. Or use only the devcontainer setup?

@vtz
Copy link
Owner

vtz commented Jan 8, 2026

@chheis would you mind rebasing your PR so that I can approve it? What are the errors you're having with interactive mode? I can help to fix it.

@chheis
Copy link
Author

chheis commented Jan 10, 2026

@chheis would you mind rebasing your PR so that I can approve it? What are the errors you're having with interactive mode? I can help to fix it.

@vtz Merged the newest changes from your main branch.

The issue with the interactive mode is that I wanted to use your dev tools installation script, instead of putting them all in the dev container script. (Avoid double work)
But while I am enhancing your scripts with a parameter for CI they where not working as I expected.
Directly with post init scripts it was working fine, setting up the tool environment in the dev container, working with Codespaces is working as well (what i normally prefer)

So I think it would be up to you, to decide which way you like to go:

  1. CI first with dev container (easy to setup the build workflows) also with prebuild/released devcontainer images
  2. Workstation build first (with interactive scripts)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants