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

← Operating Neon Law Navigator

Environment Matrix

Chapter 5 of 8 · Section 34 of 61

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: application and workflow connections
  • 32. PostgreSQL with AGE and DBOS
  • 33. Application authorization above PostgreSQL
  • 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. One application container with DBOS
  • 48. Security architecture

7. Operate billing

  • 49. Choose the payor and submission channel
  • 50. Prepare and review the bill
  • 51. Submit once and reconcile payment
  • 52. Classify client funds before collection
  • 53. One Stripe account per USD payout destination
  • 54. Turn on the route and set the Firm key
  • 55. Verify before accepting trust payments

8. Ship the Instance

  • 56. Ship and verify
  • 57. Point your domain at the instance (optional)
  • 58. Drive it from the CLI
  • 59. Make it yours — white-label under your own brand
  • 60. First-ship lessons
  • 61. Canonical references

Deployed runtime: core web and worker wiring

ConcernEnvironment variables
Profile fenceNAVIGATOR_ENVIRONMENT, NAVIGATOR_CI_HARNESS, NAVIGATOR_CREDENTIAL_ENVIRONMENT
Sample mattersNAVIGATOR_SIMULATED_MATTERS
PostgreSQLNAVIGATOR_POSTGRES_HOST, NAVIGATOR_POSTGRES_PORT, NAVIGATOR_POSTGRES_DATABASE
Application loginNAVIGATOR_POSTGRES_USER, NAVIGATOR_POSTGRES_PASSWORD
Application TLSNAVIGATOR_POSTGRES_SSLMODE, NAVIGATOR_POSTGRES_ROOT_CERT
DBOS connectionNAVIGATOR_DBOS_HOST, NAVIGATOR_DBOS_PORT, NAVIGATOR_DBOS_DATABASE
DBOS loginNAVIGATOR_DBOS_USER, NAVIGATOR_DBOS_PASSWORD
DBOS TLSNAVIGATOR_DBOS_SSLMODE, NAVIGATOR_DBOS_ROOT_CERT
DBOS executorNAVIGATOR_DBOS_EXECUTOR_ID
Workflow ingressNAVIGATOR_DBOS_INGRESS_URL, NAVIGATOR_DBOS_INGRESS_TOKEN
Workflow health listenerWORKFLOWS_SERVICE_HEALTH_LISTEN
HTTP identityPORT, NAV_BASE_URL, CANONICAL_HOST, NAVIGATOR_RATE_LIMIT_PER_MIN
Branding and public assetsNAVIGATOR_CUSTOM_BRANDING, NAVIGATOR_ASSET_BASE_URL
Storage driverNAVIGATOR_STORAGE_BACKEND, NAVIGATOR_STORAGE_ENDPOINT, NAVIGATOR_STORAGE_REGION
Documents/exportsNAVIGATOR_DOCUMENTS_BUCKET, NAVIGATOR_STORAGE_BUCKET, NAVIGATOR_EXPORTS_BUCKET
Other bucketsNAVIGATOR_ASSETS_BUCKET, NAVIGATOR_LFS_BUCKET
Filesystem storageNAVIGATOR_STORAGE_FS_ROOT
Entity Workspace DrivePer-Workspace Drive coordinates listed below
Generic S3 keyNAVIGATOR_STORAGE_ACCESS_KEY, NAVIGATOR_STORAGE_SECRET_KEY
Temporary S3 tokenNAVIGATOR_STORAGE_SESSION_TOKEN
Assets S3 keyNAVIGATOR_ASSETS_ACCESS_KEY, NAVIGATOR_ASSETS_SECRET_KEY
LFS S3 keyNAVIGATOR_LFS_ACCESS_KEY, NAVIGATOR_LFS_SECRET_KEY
Exports S3 keyNAVIGATOR_EXPORTS_ACCESS_KEY, NAVIGATOR_EXPORTS_SECRET_KEY
Iceberg-archive bucketNAVIGATOR_ARCHIVES_BUCKET
Iceberg-archive S3 keyNAVIGATOR_ARCHIVES_ACCESS_KEY, NAVIGATOR_ARCHIVES_SECRET_KEY
SessionsSESSION_SECRET
Worker listenerWORKFLOWS_SERVICE_LISTEN
Telemetry and log filteringOTEL_EXPORTER_OTLP_ENDPOINT, OTEL_SERVICE_NAME, RUST_LOG
Image-baked release identityNAVIGATOR_RELEASE_TAG, NAVIGATOR_GIT_SHA, NAVIGATOR_BUILD_TIME

Presenter notes

These are the process-level coordinates shared by Kubernetes manifests and non-Kubernetes installs. Production requires GCS and rejects NAVIGATOR_STORAGE_ENDPOINT; the dev profile may use disposable storage, while every hosted deployment's GCS also rejects an emulator endpoint. SESSION_SECRET must contain at least 32 bytes. The worker reads the same database, document bucket, email backend, branding bundle, and deployment profile as web so a journaled step never crosses environments. Published images bake the release identity in; local source builds leave it unknown.

The Neon Law-controlled Workspace service account has domain-wide delegation and no key: the organization policy forbids service-account keys, so the web pod's runtime identity signs each delegation as that account. Drive ingest reads NAVIGATOR_DRIVE_NEON_LAW_PROJECTS_DRIVE_ID, NAVIGATOR_DRIVE_NEON_LAW_DELEGATED_USER, and NAVIGATOR_DRIVE_NEON_LAW_SERVICE_ACCOUNT, the account's email, which ops ship derives from NAVIGATOR_DRIVE_GCP_SERVICE_ACCOUNT_ID. The two Projects-root variables are NAVIGATOR_DRIVE_NEON_LAW_PRODUCTION_PROJECTS_ROOT_FOLDER_ID and NAVIGATOR_DRIVE_NEON_LAW_STAGING_PROJECTS_ROOT_FOLDER_ID; configure each only in the approved operator-managed environment that uses that root.

NAVIGATOR_CALENDAR_NEON_LAW_OWNER supplies the bootstrap Google Workspace mailbox. An Owner can save a separate mailbox for the Firm in Firm Settings.

The typed workspace map selects a distinct Projects root for each configured deployment. An unknown deployment fails closed rather than borrowing another root. Drive ingest is optional: configure the shared Drive ID and delegated user together with the matching Projects-root ID, or omit the shared Drive ID and root. The regional GCP command enables the Drive and Admin SDK APIs, but a Workspace administrator must still grant domain-wide delegation and create the selected Drive root.

For each deployment, setup creates the identity named by NAVIGATOR_DRIVE_GCP_SERVICE_ACCOUNT_ID with no runtime GCP roles, and grants the runtime identity roles/iam.serviceAccountTokenCreator on it. Complete the global Workspace attachment once:

  1. Read that service account's OAuth client ID:

    
    gcloud iam service-accounts describe \
      "$NAVIGATOR_DRIVE_GCP_SERVICE_ACCOUNT_ID@$NAVIGATOR_GCP_PROJECT_ID.iam.gserviceaccount.com" \
      --project "$NAVIGATOR_GCP_PROJECT_ID" --format 'value(oauth2ClientId)'
    
  2. In the selected Workspace Admin console, authorize that client ID for each scope the deployment uses — https://www.googleapis.com/auth/drive, https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/contacts. Do not grant a broader Admin SDK scope merely because the API is enabled.

  3. Create that deployment's otherwise-empty Projects shared drive and record its ID. Staging creates its own drive, separate from production's.

  4. Set the row's *_DELEGATED_USER with hudson ops deployments set, and its *_PROJECTS_DRIVE_ID when Drive ingest is wanted, then roll with hudson ops ship. Create no key for the account.

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.19GitHub stars 6