Add Vercel Configuration #541
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for docs-rapids-ai ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for docs-rapids-ai ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Closed
This PR adds Vercel configuration files to the repository.
the current site exceeds the file limits for deployments with the Vercel CLI
exactlyallan
approved these changes
Sep 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds Vercel configuration files to the repository.
I refrained from adding the Vercel deployment to our existing deploy.yaml workflow because the site's current deployment size (~75,000 files) exceeds the file limit of 15,000 for Vercel CLI deploys.
Therefore, Vercel won't really be used in production for this repository until after the docs content is merged into the
rapids.airepository. At that point, this repository will effectively be just a collection of redirects that point to rapids.aiNote, this PR required updating some dependencies to get it building correctly on Vercel.