Set up Cursor Cloud development environment#318
Draft
lucaspar wants to merge 2 commits into
Draft
Conversation
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.
Summary
Sets up the Cloud Agent development environment for this monorepo and validates it end-to-end against the core product (the Gateway Django web app + REST API). Adds an
AGENTS.mdwith durable, non-obvious startup/run caveats for future agents. The only code change is the newAGENTS.md; all other setup is captured in the VM environment (system deps) and the startup update script (hostuvdeps).What was installed
fuse-overlayfsstorage driver,containerd-snapshotterdisabled for Docker 29,iptables-legacy).just,uv(symlinked into/usr/local/bin),postgresql-client, andlibpq-dev/build-essential(needed to buildpsycopg[c]in the hostuvvenv).uvvirtualenvs forgateway(--extra local) andsdk.Update script (startup dependency refresh)
Services / verification
The Gateway local stack was deployed via
SDS_SKIP_SFS=true ./scripts/deploy.sh local(RustFS is the local primary S3 store; SeaweedFS is an optional secondary and is skipped locally). All required services came up: Django app, Postgres, Redis, OpenSearch, RustFS, Celery worker + beat, node/webpack, nginx.just pre-commitjust test-pyjust test-jsSDS_SKIP_SFS=true ./scripts/deploy.sh localHello-world walkthrough
Logged in to the web UI at
http://localhost:8000and generated an API key (the core Gateway↔SDK action).gateway_login_and_generate_api_key.mp4
Logged-in API Keys page
Generated API key success page
Known non-blocking caveat
sds-gateway-local-nginxreportsunhealthyonly because its healthcheckwget http://localhost/healthzresolves to IPv6::1while nginx listens on IPv40.0.0.0:80. nginx serves correctly over IPv4 and the app is reached directly on port8000. Documented inAGENTS.md.To show artifacts inline, enable in settings.