Repository navigation
Conversation
Teach cloud agents how to install Plane and boot the local stack: Node 22.22.0, pnpm 11.10.0, Docker, and the web, admin, space, live, and API dev servers.
|
|
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Keep the image to Node, pnpm, and Docker. install.sh is a safe setup.sh plus compose image pulls, and start.sh is docker compose up -d for the local API. Frontends stay on pnpm dev.
This branch has not been deployed
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.
Description
Cloud Agent setup for Plane follows the local flow in CONTRIBUTING.md. The image is only the toolchain a Cloud Agent needs (Node 22.22.0 from
.node-version, pnpm 11.10.0, Docker with fuse-overlayfs and iptables-legacy). It does not install Plane or boot the app.bash .cursor/install.shis a safe./setup.sh: copy missing.envfiles from the examples, addSECRET_KEYonly whenapps/api/.envdoes not already have one, andpnpm install --frozen-lockfile. It also pulls and builds the imagesdocker-compose-local.ymlneeds. Existing env files are left alone, and a secondSECRET_KEYis never appended.bash .cursor/start.shrunsdocker compose -f docker-compose-local.yml up -dand waits until the API is healthy on :8000.frontendterminal runspnpm dev(web :3000, admin :3001, space :3002, live :3100). Thebackendterminal follows compose logs for the API, worker, and beat.When
stack.shlands in the repo, install and start should call that script instead of these compose and pnpm steps. This PR does not addstack.sh.Type of Change
Screenshots and Media (if applicable)
Test Scenarios
Verified on this Cloud Agent VM after the CONTRIBUTING alignment:
bash .cursor/install.shexited 0. Node v22.22.0, pnpm 11.10.0,pnpm install --frozen-lockfilewas already up to date, infrastructure images pulled, and the local API image build was cached. Existing.envfiles were unchanged (same hash before and after) andapps/api/.envstill has a singleSECRET_KEYline.bash .cursor/start.shrandocker compose -f docker-compose-local.yml up -dand reportedready http://127.0.0.1:8000/api/instances/ (200).bash .cursor/run-frontend.shranpnpm dev.http://127.0.0.1:3000/returned HTTP 200.http://127.0.0.1:3001/god-mode/returned HTTP 200. The admin root returns HTTP 302 and following that redirect returns HTTP 200. Live loggedExpress server has started at port 3100.References
Sriram approved aligning this environment with CONTRIBUTING.md on the same branch. Saved Cloud Agent environment:
82b010f6-c02b-11f1-bb68-864e54d14197.