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

← Operating Neon Law Navigator

Ship the Instance

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

Point your domain at the instance (optional)

hudson ops gcp setup reserves a gateway IP but does not change DNS. Keep DNS provider credentials in the operator's secret store and use the provider's reviewed change workflow. For each selected row, load its private configuration from $NAVIGATOR_DEPLOYMENTS_DIR/deployments/$ROW/config.toml, inspect the planned record changes, and verify the hostname, gateway address, certificate, and OAuth redirect URI together before applying them. Do not use copied record IDs or addresses from workshop material; those values belong to the operator's current DNS account and private row configuration.

After the change, verify provider state and public resolution, then check /readyz, /version, and the browser surface for the selected host. See docs/dns.md for the supported provider workflow.

Presenter notes

Keep DNS visibly outside deployment configs. Provider tokens belong in the operator's secret store, and each DNS change must be reviewed against the selected row before it is applied.

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