Repository navigation
Conversation
dfilimon
force-pushed
the
coder-compose-setup
branch
from
November 4, 2026 13:23
67caa0b to
fa6c47a
Compare
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
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.
The existing source setup assumes Ubuntu with system package installation. Add a separate Coder development Compose configuration whose image references, Temporal entrypoint and writable data location can be adapted to internal registry images.
Run
./scripts/dev/coder/dev.sh fullto use it. The wrapper selects the same Compose file for infrastructure startup, initialization, status and teardown while retaining the existing development defaults for ordinary./dev.shusers. Internal images must provide the expected upstream executables, including the Temporal CLI.Validation:
npm run check:devpassed (39 existing tests).