Every pull request gets its own running copy of your app at a unique URL. Share it with your team, click around before you merge, and know that what reviewers see is exactly what will ship.Documentation Index
Fetch the complete documentation index at: https://docs.withnubo.com/llms.txt
Use this file to discover all available pages before exploring further.
How it works
- A teammate opens a pull request against your tracked branch.
- Nubo builds the PR’s branch and runs it alongside your production Frame.
- The preview gets its own Nubo-assigned subdomain, distinct from the production Frame’s URL.
- Push a new commit to the PR? Nubo rebuilds the preview.
- Merge or close the PR? Nubo tears the preview down.
Enable or disable previews
Open the Frame’s CI/CD tab. “Preview deployments” is on by default. Turn it off if you don’t want previews on a particular Frame. From the API:Finding the preview URL
Check the Deployments tab on the Frame; previews show up there labeled with the PR number. Direct link support in the GitHub PR UI (with a comment from Nubo) is on the roadmap.What’s different from a production deploy
A preview is a separate runtime with its own URL, but otherwise behaves like any other Frame:- Build steps, language detection, and runtime behavior are identical.
- Project-scoped environment variables are available in the preview. Frame-scoped ones stay with the production Frame; promote them to the Project level if you need them in previews.
- Build logs are captured the same way.
- Custom domains are not attached to previews - previews use their Nubo-assigned URL only.
Cleanup
Previews are torn down automatically when the PR is closed (merged or not). If you need to wipe a preview manually before that, delete the corresponding entry from the Deployments tab.Related
CI/CD
Tune how Nubo builds on every push
Deployments
See builds and their status per Frame
