Add button and config to deploy to Vercel #11
Merged
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 creates the necessary vercel.json config and template URL so that users can easily deploy opendocs to Vercel using the Vercel default deploy button.
This PR addresses Issue #10.
Ignore the 30 commits 😅
I tried a LOT of Vercel configurations before I got one that worked. It turns out that deploying a monorepo to Vercel isn't always easy. I wound up with 8 test deployments (and GitHub repos) on my Vercel account and two on GitLab.
In the files changed tab, you can see what you need.
.npmrc
file (took a long time to find out that was an issue, since Vercel decided to error without any logs on it).demo-*
ones are less important.nextjs
framework pointer and throws an error if it's not in your dependencies.turbo.json
file really changed, it just got formatted, and it was more readable, so I left it that way.vercel.json
file, so we wound up with an annoyingly small but necessary Vercel file.Existing deployment: https://opendocs-next.vercel.app