-
Notifications
You must be signed in to change notification settings - Fork 147
Enables local queue origin config via Nitro runtime #629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Enables local queue origin config via Nitro runtime #629
Conversation
Allows configuring the local world queue origin using Nitro's runtime config. This enables users to specify custom domains, ports, or environments via runtime config, especially useful in Nuxt applications. It adds a Nitro plugin that maps runtime config to the `WORKFLOW_LOCAL_BASE_URL` environment variable. Also, improves local world config to prioritize the `WORKFLOW_LOCAL_BASE_URL` environment variable.
🦋 Changeset detectedLatest commit: 5cc4824 The changes in this PR will be included in the next version bump. This PR includes changesets to release 14 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@claylevering is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
Moves Nuxt runtime config documentation to the local world deployment guide and removes the duplicate from getting started as it is an advanced topic. Great feedback from @adriandlam This change centralizes the information and avoids repetition.
|
@adriandlam - Thanks for the feedback and good call. Shifted it to the |
|
looks good to me but also it seems the |
Co-authored-by: Adrian <me@adriandlam.com>
Checked the logs - unsure if I'm supposed to be providing tokens to run these automations? |
ah can you see the logs in #633? they're the tests for your PR. it also fails to build locally |
|
No - unfortunately I can't - I'll see if I can figure out how to run the tests locally to check things out. You can also find me at my email addy or DM me |
Hi team! Weird Nuxt user here who is even weirder using fully qualified wildcard certs in local dev (don't ask). While I could get away with just submitting a PR to update the documentation to recommend this (which does work):
WORKFLOW_LOCAL_BASE_URL=https://dev.localdomain.com:3000 pnpm exec nuxt devI figured what the hell and let Cursor do some magic. This SHOULD allow users in the Nitro / Vite / Nuxt groups to support non-default http://localhost:3000 URLs. I say SHOULD because I haven't tried building / running the package locally. Sure hope the GH Actions work well!
Summary from Cursor / Copilot:
Allows configuring the local world queue origin using Nitro's runtime config.
This enables users to specify custom domains, ports, or environments via runtime config, especially useful in Nuxt / Vite applications.
It adds a Nitro plugin that maps runtime config to the
WORKFLOW_LOCAL_BASE_URLenvironment variable.Also, improves local world config to prioritize the
WORKFLOW_LOCAL_BASE_URLenvironment variable.