feat(devtooling): local chain, debug configs and resource controls in devcontainer (#238) - #1001
Merged
Smartdevs17 merged 1 commit intoSep 30, 2026
Conversation
… devcontainer (Smartdevs17#238) The devcontainer covered Postgres and Redis but not the rest of the acceptance criteria: there was no local blockchain node, no debug configuration, no resource allocation controls, and chain state was lost on every restart. - docker-compose: add a `stellar` service (stellar-quickstart in local mode, mirroring docker-compose.sandbox.yml) and an opt-in `evm` Hardhat service; expose CPU/memory limits and reservations for every service, overridable via DEV_*_CPUS / DEV_*_MEMORY. - volumes: persist ledger state (`stellar-data`), Hardhat cache and the Rust contract build cache so deploys survive a restart. - devcontainer.json: forward the chain and debugger ports with labels, export STELLAR_RPC_URL / SOROBAN_RPC_URL / EVM_RPC_URL, and declare hostRequirements so an under-resourced host fails fast. - debug configs: tracked templates in .devcontainer/vscode/ (the .vscode directory is gitignored) installed on create, covering backend (tsx + inspector 9229), frontend, current test file, Soroban tests, attach mode and a full-stack compound, plus stack/chain tasks. - scripts/devcontainer.sh: add `infra`, `stellar`, `evm` and a guarded `reset`. - docs: document nodes, debug configs, resource knobs and volumes. 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
|
@sandrawillow001-afk is attempting to deploy a commit to the smartdevs17's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
2 participants
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.
Closes #238.
What already existed
.devcontainer/already provided the devcontainer itself, Postgres, Redis, port forwarding, volume persistence for those two services and a one-commandscripts/devcontainer.sh.Gaps closed
stellarservice (stellar/stellar-quickstart, local mode, mirroringdocker-compose.sandbox.yml) started by default, plus an opt-inevmHardhat service behind theevmprofile.devcontainer/vscode/installed into.vscode/bypost-create.sh: backend (tsx watch+ inspector on 9229), backend without watch, current test file, Next.js, Sorobancargo test, attach mode, and a full-stack compound; plus stack/chain tasksDEV_POSTGRES_MEMORY,DEV_STELLAR_CPUS, …), plushostRequirementsso an under-resourced host fails faststellar-data(ledger state survives restarts),hardhat-cacheandcontract-target(Rust build cache)stellar/postgres/redisare arm64-native, EVM node defaults tolinux/amd64withDEV_EVM_PLATFORMoverride.vscode/is gitignored, so the debug configs live as tracked templates and are copied in on create; existing user files are never overwritten.Verification
Resource limits resolve as expected (e.g.
stellar→cpus: 2,memory: 2147483648).🤖 Generated with Codebuff