-
SummaryI'm trying to find the docs for v1. (Keen to upgrade at some point but I don't need extra work right now...) Additional informationI looked on https://turbo.build/repo/docs and searched for v1 but didn't see anything or any version switch I suppose I can find a way to build it locally, but much easier if this is already in the wild. I also tried the Wayback Machine, but I'm getting a lot of 500 errors at the moment. ExampleNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
I too was annoyed by this, so I deployed my own on Github Pages: It took a while to build and deploy this, actually. I was seeing the same problem as described here - vercel/next.js#45443 - but the actual issue was: the To fix all of this, I changed the gh-pages deployment to a Github Actions based one, and set it up to deploy all of my static assets (I was committing the "export" of the next.js site after it was completed). Took forever but hopefully I never have to touch this again, and this can help other people looking for the v1 docs. |
Beta Was this translation helpful? Give feedback.
-
|
Wow, good effort... I managed to upgrade my own project several months back, but looks like there are other people looking for this. |
Beta Was this translation helpful? Give feedback.
I too was annoyed by this, so I deployed my own on Github Pages:
It took a while to build and deploy this, actually. I was seeing the same problem as described here - vercel/next.js#45443 - but the actual issue was: the
_next/folder wasn't being included in the default gh-pages build/deploy process. Because it uses jekyll under the hood, by convention it was looking for a_sites/directory.To fix all of this, I changed the gh-pages deployment to a Github Actions based one, and set it up to deploy all of my static assets (I was committing the "export" of the next.js site after it was completed).
Took forever but hopefully I never have to touch …