Shared dev VM on GCP
To speed up hackathon iteration, all three engineers will SSH into a single shared GCP VM. Each dev gets their own Linux user, clones the lawn repo into their home, and syncs through GitHub.
What we need from Mohnaa
Recommended VM spec
| Parameter |
Value |
Why |
| Machine type |
e2-medium (2 vCPU, 4 GB RAM) |
Enough for Python + Node + agent prototype; ~$25/mo |
| OS |
Ubuntu 22.04 LTS |
Standard, broad package support |
| Disk |
30 GB pd-balanced |
Repo + deps + logs fit comfortably |
| Region |
asia-south1 (Mumbai) |
Closest to Mohnaa; lower SSH latency for primary user |
| Firewall |
SSH only (port 22, IAP or IP allow-list) |
Closed by default |
| External IP |
Ephemeral OK |
Free; OS Login or hostname avoids IP churn issue |
Cost estimate: ~$25/mo always-on, ~$10/mo if stopped overnight. For 21 days: ~$15-20 burn → leaves $80+ of credit for Cloud Run deploy + Gemini calls.
Linux users (3 separate accounts — not a shared user)
Each engineer keeps their own git config, history, and clone. No "who pushed this?" confusion.
| User |
Public key source |
forenly |
I (Forenly) will paste my public key as a comment below |
mohnaa |
Your own key |
macb |
macb-cilson will paste their public key as a comment below |
Add all three to the sudo group (apt installs) and docker group (for Cloud Run image builds later).
Setup checklist for Mohnaa (post-creation)
Info to send back (comment on this issue)
- VM hostname or external IP
- Example SSH command —
ssh forenly@<host>
- Auth method — OS Login or classic SSH keys
- GCP project ID (needed for
gcloud configuration)
- Billing dashboard link (so we can monitor credit burn together)
What Forenly + macb-cilson will do
Post our SSH public keys as comments on this issue. If we don't have a key yet:
ssh-keygen -t ed25519 -C "<github-handle>@lawn-dev"
cat ~/.ssh/id_ed25519.pub
How GitHub sync will work on the VM
Each user, once SSH'd in:
gh auth login # authenticate to GitHub
git clone https://github.com/forenly-ai-systems/lawn.git
cd lawn
git config user.name "<github-display-name>"
git config user.email "<email>"
Two engineers editing the same branch at the same time → coordinate via tmux or just stagger via branches. The branch + PR pattern from CONTRIBUTING.md still applies — GitHub remains the source of truth.
Discord pin
Once VM is live, the connection details will be pinned in #lawn-prs so the team can rejoin anytime.
Priority: high — blocking real coding work. Aim to have this up within 24 hours.
Shared dev VM on GCP
To speed up hackathon iteration, all three engineers will SSH into a single shared GCP VM. Each dev gets their own Linux user, clones the
lawnrepo into their home, and syncs through GitHub.What we need from Mohnaa
#lawn-prsRecommended VM spec
e2-medium(2 vCPU, 4 GB RAM)pd-balancedasia-south1(Mumbai)Cost estimate: ~$25/mo always-on, ~$10/mo if stopped overnight. For 21 days: ~$15-20 burn → leaves $80+ of credit for Cloud Run deploy + Gemini calls.
Linux users (3 separate accounts — not a shared user)
Each engineer keeps their own git config, history, and clone. No "who pushed this?" confusion.
forenlymohnaamacbAdd all three to the
sudogroup (apt installs) anddockergroup (for Cloud Run image builds later).Setup checklist for Mohnaa (post-creation)
apt update && apt upgradevenv, Node 20 + npm, git, build-essentialgcloudCLI) — needed for Gemini + MongoDB MCP latertmux(in case we want a shared session)~/.ssh/authorized_keysfor each userInfo to send back (comment on this issue)
ssh forenly@<host>gcloudconfiguration)What Forenly + macb-cilson will do
Post our SSH public keys as comments on this issue. If we don't have a key yet:
How GitHub sync will work on the VM
Each user, once SSH'd in:
Two engineers editing the same branch at the same time → coordinate via tmux or just stagger via branches. The branch + PR pattern from
CONTRIBUTING.mdstill applies — GitHub remains the source of truth.Discord pin
Once VM is live, the connection details will be pinned in
#lawn-prsso the team can rejoin anytime.Priority: high — blocking real coding work. Aim to have this up within 24 hours.