How to Upgrade an Entire App in Vercel
Answered
Asiatic Lion posted this in #help-forum
Asiatic LionOP
I have an app built with Next.js 12 and we are now planning to upgrade to Next.js 14. This upgrade includes new functionalities and design changes. We have separated the repositories, so my question is: Is there a way to deploy 2 repositories in the same project on Vercel, or how could I create a feature flag to direct, for example, 10% of users to the new version and, based on its performance, gradually increase it to 100%?
Answered by joulev
a project only supports one repo.
what you are looking for is a/b testing. you can implement this by deploying the new version to a different domain, say beta.domain.com, then in the main domain.com, use a middleware to rewrite requests to the beta domain
what you are looking for is a/b testing. you can implement this by deploying the new version to a different domain, say beta.domain.com, then in the main domain.com, use a middleware to rewrite requests to the beta domain
2 Replies
@Asiatic Lion I have an app built with Next.js 12 and we are now planning to upgrade to Next.js 14. This upgrade includes new functionalities and design changes. We have separated the repositories, so my question is: Is there a way to deploy 2 repositories in the same project on Vercel, or how could I create a feature flag to direct, for example, 10% of users to the new version and, based on its performance, gradually increase it to 100%?
a project only supports one repo.
what you are looking for is a/b testing. you can implement this by deploying the new version to a different domain, say beta.domain.com, then in the main domain.com, use a middleware to rewrite requests to the beta domain
what you are looking for is a/b testing. you can implement this by deploying the new version to a different domain, say beta.domain.com, then in the main domain.com, use a middleware to rewrite requests to the beta domain
Answer
@joulev a project only supports one repo.
what you are looking for is a/b testing. you can implement this by deploying the new version to a different domain, say beta.domain.com, then in the main domain.com, use a *middleware* to *rewrite* requests to the beta domain
Asiatic LionOP
ok, thanks joulev:)