Skip to content

Commit da0963f

Browse files
sspickleclaude
andcommitted
docs(readme): add a "Coming back to this repo?" section
Four steps to get oriented (refreshall.sh, make, current plan, what's live) and the three traps: one shared database, two GCP projects, and runners on a separate origin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QNw6KLiif2r9zSoSQug4iL
1 parent e7fa29c commit da0963f

1 file changed

Lines changed: 17 additions & 0 deletions

File tree

‎README.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,23 @@
33
Management repo for the Web VPython stack. The four active sub-repos are
44
separate git repositories cloned into this directory.
55

6+
## Coming back to this repo?
7+
8+
1. `bash refreshall.sh`: pull this repo and every sub-repo (fast-forward only).
9+
2. `make`: the menu of everything you can run (serve, deploy, build, git).
10+
3. Current plan: [glowscript.org → webvpython.org migration](docs/superpowers/specs/2026-09-26-glowscript-to-webvpython-migration.md).
11+
Work-in-progress notes for the runners are in [AGENTS.md](AGENTS.md).
12+
4. What's live: `curl -s https://beta.webvpython.org/config` shows the deployed `git_commit`.
13+
14+
Things that bite:
15+
- **One database for everything.** glowscript.org (Classic GAE) and beta.webvpython.org both
16+
use the Datastore in GCP project `glowscript`. `make serve-prod` writes to it too.
17+
- **Two projects.** Cloud Run (`flaskdstorehost`) and the database are in `glowscript`; the
18+
runner and docs buckets are in `glowscript-py38`. Deploy scripts pin their targets, so the
19+
active gcloud config doesn't matter.
20+
- **Runners stay on a separate origin** from the IDE. They run student code; never serve them
21+
from the IDE's own domain.
22+
623
## Sub-repos
724

825
| Directory | Repo | Purpose |

0 commit comments

Comments
 (0)