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

← Operating Neon Law Navigator

Environment Matrix

Chapter 5 of 8 · Section 25 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

The deployment that says its matters are sample

NAVIGATOR_SIMULATED_MATTERS is the second selector, and it answers a different question from the first. The profile above decides which runtime wiring a boot gets; this decides whether the matters in front of a visitor are invented.

Left unset or empty, the simulated-matters announcement follows the profile. Exactly true or false overrides that announcement; other values are rejected. This setting does not insert, replace, or remove matter records. The boot profile alone controls sample-fixture insertion.

The override that matters is true under a production profile. A hosted demonstration row may use a production runtime profile, so it must explicitly enable simulated matters in its own $NAVIGATOR_DEPLOYMENTS_DIR/deployments/${ROW}/config.toml:


NAVIGATOR_SIMULATED_MATTERS = "true"

The value enables the site-wide sample-matters announcement. It does not populate sample-litigation, sample-transactional, or sample-estate on a production-profile boot. Verify the demonstration portfolio separately before sharing a hosted row; a banner is not proof that its data is synthetic.

It is a coordinate, not a credential, so it lives in config.toml beside the buckets and hostnames rather than in that deployment's secrets.enc.yaml. Adding it needs no SOPS re-encryption on either row.

Other hosted rows may state "false" explicitly for documentation. The code already reads a missing value as false under a production profile, and ops ship renders false into the web env when a deployment's config omits the key, so the substitution is deliberately optional: a config that never mentions it still renders and still ships. A key that could halt a production rollout by being deleted would be a worse failure than the one it guards against.

Presenter notes

Two selectors, two questions. Ask the room which one decides whether a visitor sees invented clients — the answer is not the one whose name contains "environment". Then point out that staging's runtime profile is production , and let the operator identify the release ring by checking NAVIGATOR_STAGING in the selected deployment row. That is why there is a second selector at all rather than a third value on the first one.

The banner is the part worth dwelling on. It distinguishes a demo environment from one that may hold real files.

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