Replies: 2 comments 3 replies
-
|
Hello @Manubi , The team is currently working on this and it should arrive in the upcoming weeks. The idea is to offer "multi-env" support as you described. Perhaps this can assist you while we don't release this. |
Beta Was this translation helpful? Give feedback.
-
|
It would be really appreciated if the docs could have been updated to reflect this. Just a little pointer along the lines of 'this feature is completely standard but we don't support it yet - it's coming soon though so don't worry!'. I spent the past 24 hours trying crack pot solutions online and I'd like that time back! |
Beta Was this translation helpful? Give feedback.
-
|
You can always send us an email ([email protected]) and we will certainly give you a hand. |
Beta Was this translation helpful? Give feedback.
-
|
@Jakkc Take a look at https://github.com/UnlyEd/next-right-now, it's built with such workflow in mind. It may be "too much" but you can use it as a learning resource still :) (and the Zeit team is really great at helping out too!) |
Beta Was this translation helpful? Give feedback.
-
|
@Manubi Check out https://github.com/UnlyEd/next-right-now, it does exactly that. Maybe you can use it as a boilerplate if you're starting from scratch, or learning from how we did things to support multi-env. :) |
Beta Was this translation helpful? Give feedback.
-
Hey,
what is the best solution to get a setup where I can set different env variables for the different environments and can deploy them to different urls such as http://dev.my-domain.com, http://staging.my-domain.com...
Ideally if i push the dev branch into the staging branch it will push it to http://staging.my-domain.com
How do you guys do it?
Beta Was this translation helpful? Give feedback.
All reactions