mattrguerra.comHouston area
Matt Guerra
  1. 01AI & Automation
  2. 02Photography
  3. 03Design
  4. 04About
  5. 05Notes
  6. 06Contact
Back to the systems

mattrguerra/meridian-ops-boardmainPrivate on GitHub, published here in full

credentials.example.sh

Shell4.9 KB98 lines

credentials.example.sh

  1. # Meridian dashboard credentials. Copy these exports into your shell profile.
  2. #
  3. # Not a .env file. This repo has no .env reader, deliberately: a credentials
  4. # file in the working tree is readable by every tool and agent that touches the
  5. # repo, and a secret that has been read is a secret that has to be rotated.
  6. # Keeping them in the shell profile keeps them out of the tree entirely.
  7. #
  8. # Which file:
  9. #
  10. # zsh (macOS default since Catalina) ~/.zshrc interactive shells
  11. # ~/.zshenv every shell, incl. cron
  12. # bash ~/.bash_profile or ~/.bashrc
  13. # tcsh / csh ~/.cshrc uses `setenv NAME value`,
  14. # not the `export` syntax below
  15. #
  16. # Check which shell you are actually in: echo $SHELL
  17. #
  18. # If you ever run this from cron or a launchd job, use ~/.zshenv: ~/.zshrc is
  19. # only sourced for interactive shells, and a scheduled run would find nothing.
  20. #
  21. # After editing, open a new terminal or `source` the file. Existing terminals
  22. # keep the old values, and nothing in the repo can detect that.
  24. # --- Ninety (90) -------------------------------------------------------------
  25. # Personal Access Token: Ninety > User Settings > Developer Settings.
  26. # Must belong to a company Owner or Admin. GET /todos/company returns 403 for
  27. # every other role, and that endpoint is the entire company view.
  28. # Shown once at generation. Record the expiry date in a calendar.
  29. # Generating a new token invalidates the previous one.
  30. export NINETY_TOKEN=""
  32. # Optional. Only if Ninety changes the base URL.
  33. # export NINETY_BASE_URL="https://api.public.ninety.io/v1"
  34. # export NINETY_RPS=20
  36. # --- Bitrix24 ----------------------------------------------------------------
  37. # Inbound webhook URL including the token path segment. Read scopes: crm, task.
  38. # https://yourcompany.bitrix24.com/rest/<user-id>/<token>/
  39. export BITRIX_WEBHOOK_URL=""
  41. # --- Plinth ------------------------------------------------------------------
  42. # Read-only Plinth API key. Plinth caps at 10 requests / 10 seconds; the client
  43. # throttles rather than failing, so a wide window just runs slower.
  44. export PLINTH_API_KEY=""
  46. # --- Anthropic (the briefing model) ------------------------------------------
  47. # Create in a dedicated Console workspace with its own monthly spend limit.
  48. # Workspace-owned keys survive the creator being removed; personal keys do not.
  49. # One run a day costs little; set a limit a few times the expected monthly
  50. # spend so a runaway loop stops long before it becomes a bill.
  51. export ANTHROPIC_API_KEY=""
  52. export ANTHROPIC_MODEL="claude-opus-5"
  53. export ANTHROPIC_BASE_URL="https://api.anthropic.com/v1"
  55. # Point ANTHROPIC_BASE_URL at a local OpenAI-compatible server instead
  56. # (LM Studio, mlx_lm.server, Ollama, vLLM) and the transport switches itself:
  57. # export ANTHROPIC_BASE_URL="http://127.0.0.1:1234/v1"
  58. # export ANTHROPIC_MODEL="qwen3-30b-a3b-instruct"
  60. # --- Fathom (meeting commitments) --------------------------------------------
  61. # One key per person; Fathom has no org-level key. A key returns its owner's
  62. # recordings plus meetings Fathom shares with that user by a mechanism the API
  63. # does not describe (`shared_with` reads `no_teams` on all of them), so every
  64. # key comes back with more meetings than its owner recorded.
  65. #
  66. # Two consequences, and they pull in opposite directions:
  67. #
  68. # Coverage. The board sees the union of what its keys return, so people who
  69. # hold no key still have meetings on the board. Whether all of their
  70. # recordings arrive cannot be known from here.
  71. #
  72. # Access. Fathom's own permissions do not gate this board. Everything a key
  73. # can see lands in the snapshot, and the board's own participant filter is the
  74. # only thing keeping a meeting off a non-attendee's page. Do not add a key
  75. # that was not deliberately handed over for this purpose.
  76. #
  77. # Create at Fathom > Settings > API. Which names are read is decided by
  78. # config/fathom-keys.ts, not by this file: exporting FATHOM_KEY_ROSA with no
  79. # line in that config does nothing.
  80. #
  81. # Also needed in the Worker. The 6:00 AM CT cron runs in Cloudflare, which
  82. # cannot see your shell. Each key goes in twice:
  83. # cd apps/worker && npx wrangler secret put FATHOM_KEY_INES
  84. export FATHOM_KEY_SAM=""
  85. export FATHOM_KEY_INES=""
  86. export FATHOM_KEY_THEO=""
  88. # --- Gmail, for the consolidated inbox tab -----------------------------------
  89. # Nothing goes here. The inbox's Gmail credentials live only in Worker
  90. # secrets: per-mailbox refresh tokens (GMAIL_REFRESH_*, minted by
  91. # `pnpm inbox:auth`, which pipes them straight into `wrangler secret put`) or a
  92. # service-account key (GMAIL_SA_EMAIL and GMAIL_SA_KEY).
  93. #
  94. # Those open other people's mailboxes, so they are deliberately not something
  95. # the repo, this file, or your shell profile ever holds.
  97. # --- misc --------------------------------------------------------------------
  98. # export DEBUG=true # logs every request path to stderr. Noisy.