Try working around Nitro/Netlify shenanigans #76
Closed
Conversation
This file contains hidden or 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
✅ Deploy Preview for directus-docs-v2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
With this netlify BS i've already hit the lfs bandwidth limit
|
Conclusion: It does not work. nitrojs/nitro#1484 wrecks the ability to have the docs auto-deploy to netlify on commits to |
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.
Apparently Nitro has some magic preset that messes up the config and makes it behave differently than local when it runs on Netlify. The Netlify preset apparently has a known limitation when used with
baseURL(see nitrojs/nitro#1484).I'll have to trial and error through this, and didn't want to spam the main branch anymore than I already have