Add a Conductor run script and drop the VSCode tasks - #39
Merged
Conversation
Spotlight testing syncs the active workspace into the repository root, and the single `dev` run script serves the whole stack from there: docker compose, prisma migrate and generate, then worker, scheduler and frontend under one `nx run-many`. Every workspace therefore shares one node_modules, one docker stack and one database, while `setup.sh` keeps lint, build and test working per workspace. Local dev values live in `.conductor/dev.env`, which is also handed to agents, and the compose ports move to an unusual range so they stop colliding with other projects on the same machine. The VSCode tasks that used to launch the same processes are removed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Conductor spotlight testing syncs the active workspace into the repository root, where a single
devrun script starts docker compose, applies migrations, regenerates the Prisma client, and serves worker, scheduler and frontend under onenx run-many. Every workspace therefore shares onenode_modules, one docker stack and one database, while.conductor/setup.shkeeps lint, build and test working inside each workspace. Local dev values live in.conductor/dev.env, which Conductor also passes to agents, and the compose host ports move to 47821-47826 so they stop colliding with other projects on the same machine. The VSCode tasks and extension recommendations that used to launch these same processes are removed, and the frontend's dev port now lives in its project config.🤖 Generated with Claude Code