Repository navigation
feat(devtooling): one-command devcontainer stack with all services (#794) - #987
Merged
Smartdevs17 merged 1 commit intoSep 28, 2026
Conversation
…martdevs17#794) Make the local development environment start Postgres, Redis, backend, and frontend together, and repair the container images that made that impossible. - Add backend/frontend/deps services to the devcontainer Compose file behind an app profile so the IDE flow stays lightweight while a single command brings up the whole stack - Add scripts/devcontainer.sh (up/down/logs/ps/restart/shell/config) - Fix corrupted Dockerfile.backend and Dockerfile.frontend that contained stray branch-name lines and failed to build; align the backend exposed port to 3001 - Document the one-command flow in DEVCONTAINER.md and the README 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. |
|
@sandrawillow001-afk Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Summary
Delivers a one-command local development environment that starts Postgres, Redis, backend, and frontend together, and repairs the container images that made a build impossible.
Changes
backend,frontend, and a one-timedepsinstall service to.devcontainer/docker-compose.ymlbehind theappprofile — the IDE flow (Reopen in Container) stays lightweight, while--profile appbrings up the whole stack.scripts/devcontainer.shwithup,down,logs,ps,restart,shell, andconfig.Dockerfile.backendandDockerfile.frontend— both contained stray branch-name lines (feat/print-onboarding-...,main) that made them invalid Dockerfiles. Also aligned the backend exposed port with the app default (3001).docs/DEVCONTAINER.mdand the README.Usage
scripts/devcontainer.sh up # Frontend http://localhost:3000 · Backend http://localhost:3001/api/v1Testing
docker compose -f .devcontainer/docker-compose.yml --profile app config→ valid (6 services)docker build --check -f Dockerfile.backend .andDockerfile.frontend→ no warningsbash -n scripts/devcontainer.sh→ okCloses DevTooling: Implement Local Development Environment with Devcontainers #794