Skip to content

feat(cli): add concore setup autodetect command#512

Merged
pradeeban merged 2 commits intoControlCore-Project:devfrom
avinxshKD:fix/setup-autodetect-506
Mar 26, 2026
Merged

feat(cli): add concore setup autodetect command#512
pradeeban merged 2 commits intoControlCore-Project:devfrom
avinxshKD:fix/setup-autodetect-506

Conversation

@avinxshKD
Copy link
Copy Markdown
Contributor

@avinxshKD avinxshKD commented Mar 26, 2026

Adds concore setup for first-run config.

  • Detects installed tools via existing doctor helpers

  • Writes concore.tools, concore.sudo, concore.octave

  • Supports --dry-run and --force

  • No backend behavior changes outside new command

I tested with:

python -m unittest tests.test_setup (pass)

fixes #506

@avinxshKD
Copy link
Copy Markdown
Contributor Author

@pradeeban pls look at this :P

@GREENRAT-K405
Copy link
Copy Markdown
Contributor

GREENRAT-K405 commented Mar 26, 2026

Hello @pradeeban @avinxshKD I had a doubt, I wanted to do similar thing with something like 'concore doctor --fix'
that can automatically write concore.tools in case deps are missing or are not configured.

If the deps are not installed and setup globally, we would require to install them (this would require sudo permissions which is not ideal for commands like doctor, even brew doctor doesn't do this).

But say, if the dependencies are already globally configured, then in that case won't it become unnecessary to setup concore.tools?

Just wanted to have a discussion regarding this.

@pradeeban pradeeban merged commit 7c5ea5b into ControlCore-Project:dev Mar 26, 2026
6 checks passed
@pradeeban
Copy link
Copy Markdown
Member

@GREENRAT-K405 Good question. Not sure whether I have a solid answer to that yet. Something to contemplate.

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.

3 participants