Neon LawCall +1 510 800 2090
  • Navigator
  • Notations
  • Legal Aid
  • Sign in

← Operating Neon Law Navigator

Prepare Google Cloud

Chapter 2 of 7 · Section 4 of 54

Sections

1. Intro

  • 1. Deploy your own
  • 2. Agenda

2. Prepare Google Cloud

  • 3. Bring your own project
  • 4. Dry-run first
  • 5. Private assets and domain restricted sharing
  • 6. The Navigator deployment matrix
  • 7. The `/app` mount and HTTP route ownership
  • 8. `neon` — the whole brand seam
  • 9. Live rollout checkpoint
  • 10. Set one site to one version

3. Provision the Infrastructure

  • 11. The APIs that light up
  • 12. Network and storage buckets
  • 13. How a matter's pages reach a client
  • 14. A document's bytes and authorization are separate
  • 15. A private image registry
  • 16. The cluster comes up
  • 17. What setup owns — and what follows it

4. Operate Forgejo beside Navigator

  • 18. Deploy the forge before switching repositories
  • 19. Separate people, Git transport, and machine access
  • 20. Require the gate and protected-main policy
  • 21. Bind the workflow to one Project and one commit
  • 22. Notify failures even when the manifest is broken
  • 23. Restore the repository before cutting over

5. Environment Matrix

  • 24. Three operating modes, two deployment profiles
  • 25. The deployment that says its matters are sample
  • 26. Deployment and release switches
  • 27. Workflow host and routing switches
  • 28. Capability and storage switches
  • 29. Configuration precedence: the first source wins
  • 30. Local dev controls: inputs read by `hudson dev`
  • 31. Local runtime: what `.devx/env` generates
  • 32. The store: SurrealDB
  • 33. Where SurrealDB authorization lives
  • 34. Deployed runtime: core web and worker wiring
  • 35. Deployed runtime: identity and access
  • 36. Deployed runtime: email, signatures, and billing
  • 37. Deployed runtime: repositories, content, AI, and scheduled work
  • 38. Provision and ship: variables read by the operator CLI
  • 39. Ancillary operations and opt-in test controls
  • 40. When sample data appears

6. Configure the Trust Boundaries

  • 41. Secrets: the invariants that gate the boot
  • 42. Secret access, encryption, and audit
  • 43. Sign-in: bring an OIDC provider; passwords live there, not here
  • 44. Role rings: who can do what
  • 45. Provider setup and parity across deployment rows
  • 46. The external surface — every third party, in one place
  • 47. The two service deployments
  • 48. Security architecture

7. Ship the Instance

  • 49. Ship and verify
  • 50. Point your domain at the instance (optional)
  • 51. Drive it from the CLI
  • 52. Make it yours — white-label under your own brand
  • 53. First-ship lessons
  • 54. Canonical references

Dry-run first

Before you change anything, read the plan. The --dry-run flag records every REST call and gcloud shell-out and prints them without sending traffic:


cargo run -p hudson -- ops gcp setup --project-id your-project-id --dry-run

Presenter notes

gcloud has no universal dry-run equivalent, so we built one — it prints the plan without sending traffic or touching your gcloud session. You will see the plan in order: REST calls that enable APIs, create the VPC and subnet, create a regional Cloud Router and Cloud NAT, and create six buckets. It then creates a deployment-specific Google service account and its direct Secret Manager, bucket, and signed-URL permissions. A single-project install can also provision its private Artifact Registry; an installation with a shared registry supplies that registry's project in its operator configuration. The last stages grant registry access, reserve the gateway IP and create the cluster, then attach Kubernetes Workload Identity and the cluster integrations. Read the project, region, and every resource prefix, then drop --dry-run to execute. Every step is idempotent, so a re-run after a partial failure never produces duplicates.

The CLI waits for each control-plane write at that API's own operation endpoint before starting its dependent step. Compute VPC operations are global; subnet, Router, and NAT operations are regional. Their REST resources report completion with a DONE status. Service Usage and Artifact Registry use Google long-running operations and report a true done flag. A newly enabled Compute API can still return SERVICE_DISABLED for a short propagation window after its Service Usage operation completes. The VPC step recognizes only that exact compute.googleapis.com response, prints the bounded retry count, and retries the idempotent insert for up to two minutes. Other 403 responses fail immediately because they may be real IAM or organization-policy problems. If a terminal or network interruption stops setup after GCP accepted a write, run the exact same deployment command again. Existing resources return idempotent conflicts. The pipeline generates no credential of its own, so a run — first or tenth — prints no secret for you to record. The store is SurrealDB, and its endpoint and root credentials come from your store provider.

Live setup prints nineteen secret-free stages, including the project and exact resource name:


gcp setup [ROW] 01/19 enable required APIs
gcp setup [ROW] 04/19 Cloud Router and NAT setup
gcp setup [ROW] 05/19 create private assets bucket
gcp setup [ROW] 09/19 create private applications bucket
gcp setup [ROW] 12/19 configure runtime identities and IAM bindings
gcp setup [ROW] 13/19 configure container registry access
gcp setup [ROW] 14/19 create GKE Autopilot cluster
gcp setup [ROW] 15/19 configure workload identity and cluster integrations
gcp setup [example-project] 16/19 KMS key provisioned from the selected row
gcp setup [ROW] 17/19 log retention on the logs bucket and Cloud Logging _Default
gcp setup [ROW] 18/19 release ship identity (not configured; skipped)
gcp setup [ROW] 19/19 navigator-postgres-backup-target ConfigMap in navigator
gcp setup [ROW] COMPLETE

Stage 18 runs only when --ship-deployment, --ship-repository, and --ship-environment name the row, repository, and GitHub Environment the release workflow ships from; see docs/release-automation.md.

Long-running REST writes print the service, operation ID, scoped polling path, and DONE. Output never includes the store URL, access token, service-account key, or any other secret value, and the pipeline generates no credential that would need printing.

On a newly activated project, one of these additional lines can appear between stages 1 and 2, depending on whether the activation window meets the VPC insert or its operation poll:


gcp api [compute.googleapis.com] activation is still propagating; retrying network setup (1/25)
gcp operation [Compute] operation-123: compute.googleapis.com activation is still propagating; retrying poll
View all slidesOpen display
← PreviousNext →
Neon Law
  • X opens in a new tab
  • LinkedIn opens in a new tab
  • YouTube opens in a new tab
  • API
  • Blog
  • Contact
  • Design
  • Glossary
  • Navigator
  • Notations
  • Presentations
  • Privacy
  • Team opens in a new tab
  • Terms
  • Testimonials
  • contact@neonlaw.com
  • +1 510 800 2090
  • California
    1515 20th StreetBakersfield, CA 93301
  • Nevada
    5150 Mae Anne AveSte 405-9002Reno, NV 89523
  • New York
    12 E 49th St18th FloorNew York, NY 10017
  • Washington
    1111 Main StSTE 201EVancouver, WA 98660
  • Justice Technology AssociationMission-Aligned Partner opens in a new tab
  • Proud member of Greater Vancouver ChamberGVC opens in a new tab

Attorney advertisement. Nothing here is legal advice without a signed retainer for an active project. Past results do not guarantee future outcomes.

Everyone deserves access to justice.Made with ❤️ in 🗽.

© 2026 Guieb & Shook PC

Powered by neon-law/navigator opens in a new tab26.11.17-rc.1GitHub stars 6