Skip to content

Prepare for new Orama API Keys #8012

Closed
Closed
Prepare for new Orama API Keys#8012

Description

@avivkeller
avivkeller
opened on Jul 23, 2025

We need new NEW_ environment variables for new api keys

@nodejs/web-infra

Activity

  1. github-project-automation
    added this to Node.js Websiteon Jul 23, 2025
  2. github-project-automation
    moved this to 📋 Backlog in Node.js Websiteon Jul 23, 2025

  3. MattIPv4 commented on Jul 24, 2025

    @MattIPv4
    MattIPv4
    on Jul 24, 2025 · Hidden as outdated

  4. avivkeller commented on Jul 24, 2025

    @avivkeller
    avivkeller
    on Jul 24, 2025 · Hidden as outdated
    Author

  5. micheleriva commented on Jul 24, 2025

    @micheleriva
    micheleriva
    on Jul 24, 2025 · Hidden as outdated

  6. avivkeller commented on Aug 20, 2025

    @avivkeller
    avivkeller
    on Aug 20, 2025 · Hidden as duplicate
    Author

  7. MattIPv4 commented on Aug 23, 2025

    @MattIPv4
    MattIPv4
    on Aug 23, 2025
    Member

    Noting it here for posterity, I have added new Actions secrets NEW_ORAMA_PRODUCTION_DATASOURCE_ID + NEW_ORAMA_PRODUCTION_PRIVATE_API_KEY in this repo as provided by @micheleriva.

  8. MattIPv4 commented on Aug 23, 2025

    @MattIPv4
    MattIPv4
    on Aug 23, 2025
    Member

    Will need assistance from @ovflowd or @bmuenzenmeyer to set NEXT_PUBLIC_NEW_ORAMA_PROJECT_ID=939d8d74-dbb7-4098-ac46-00325a783e17 + NEXT_PUBLIC_NEW_ORAMA_API_KEY=c1_dRV3iUW4GpJkKffpYXgCEamhWLf$_X9gfYdiVhZkVD4MCr105K0qb$BiGdg for production in Vercel, as I appear to only have access to pre-prod env vars there.

  9. avivkeller commented on Aug 23, 2025

    @avivkeller
    avivkeller
    on Aug 23, 2025
    MemberAuthor

    (Note that the values above are not sensitive, and can be plaintext in comments like this)

  10. bmuenzenmeyer commented on Aug 23, 2025

    @bmuenzenmeyer
    bmuenzenmeyer
    on Aug 23, 2025
    Contributor

    I'm out of the country right now on vacation. Be back next week

  11. MattIPv4 commented on Aug 25, 2025

    @MattIPv4
    MattIPv4
    on Aug 25, 2025
    Member

    Also noting it here for posterity, I have added new Actions secrets NEW_ORAMA_DATASOURCE_ID + NEW_ORAMA_PRIVATE_API_KEY in this repo as provided by @micheleriva. I've also set NEXT_PUBLIC_NEW_ORAMA_PROJECT_ID + NEXT_PUBLIC_NEW_ORAMA_API_KEY in Vercel for the Preview environment.

  12. MattIPv4 commented on Aug 26, 2025

    @MattIPv4
    MattIPv4
    on Aug 26, 2025
    Member

    I've also set NEXT_PUBLIC_NEW_ORAMA_DATASOURCE_ID for Preview in Vercel per #7971 (comment)

  13. MattIPv4 commented on Aug 29, 2025

    @MattIPv4
    MattIPv4
    on Aug 29, 2025
    Member

    With @ovflowd's assistance, signed into the Vercel infra account and have now set NEXT_PUBLIC_NEW_ORAMA_PROJECT_ID + NEXT_PUBLIC_NEW_ORAMA_API_KEY + NEXT_PUBLIC_NEW_ORAMA_DATASOURCE_ID in production, so we should be good to go now!

  14. MattIPv4
    closed this as completedon Aug 29, 2025
  15. github-project-automation
    moved this from 📋 Backlog to ✅ Done in Node.js Websiteon Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions