Deploying to Two Vercel Projects with a Shared GitHub Repository Across Different Branches #62175
Unanswered
chenhanting-ibuypower
asked this question in
Help
Replies: 1 comment
-
This worked for me: vercel/vercel#4622 (comment) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Deploying to Two Vercel Projects with a Shared GitHub Repository Across Different Branches
I have two Vercel projects sharing the same repository in order to create two production environments. The token belongs to my account. How can I use the project_id provided by Vercel to deploy?
vercel deploy --token gnZ2TRwYLa5pqTfe6U2J4tWE --name hyte-production-replica Vercel CLI 29.2.1 ❗️ The "--name" option is deprecated (https://vercel.link/name-flag) 🔍 Inspect: https://vercel.com/hyte/hyte/A4bR5PXwmG7MXNTiYQo8rmVCyr7K [8s] ⠴ Building
We have two projects: one is
hyte
, and the other ishyte-production-replica
.hyte-production-replica
is meant to create an environment similar to our live site. Previously, I wanted to specify the project by using the--name
tag, but it didn't work.I've checked this link, but it seems it doesn't apply to my use-case.
I have some workaround approaches, such as duplicating the repository or porting our production-replica environment over to Azure to create a completely isolated space. This ensures that when I execute the vercel deploy ... command, it won't interfere with each other.
It's still a pain for me because if I could stay completely on Vercel and use the most streamlined way, it would be great. Has anyone encountered a similar situation?
Beta Was this translation helpful? Give feedback.
All reactions