I’m not sure why the website appears twice, but both instances prompt me to create a new environment, even though there’s already a production environment from which I pulled:
Regardless of which one I click on, the “Create new environment” link redirects me to my Kinsta account. However, the production environment already exists. Is it not possible to push directly to production?
Unfortunately, it is not possible to push changes directly to a Production environment that is in MyKinsta. All pushes from DevKinsta must be sent to a Staging environment first: DevKinsta - Kinsta Integration - Kinsta® Docs
Thanks for the answer, is this a feature that could be added in the future? We sometimes push directly to production when making minor changes or doing hotfixes, so this adds an unnecessary step in our workflow.
While I can certainly put it in as a feature request, the reason this has not been put in, historically speaking, is because it’s considered potentially dangerous to the Live site. An accidental push from the local environment to the Live site could be problematic, or cause issues with the Live site that could result in data loss, particularly in the case of e-commerce sites.
You make a completely valid point, and I agree that, in most cases, pushing directly to production is not a good practice. However, I believe that ultimately, the decision should be left to the user.
Thanks for writing back. We will add this to our Feature Request list. Kinsta is currently in maintenance and security updates mode, so we can’t provide any information in regards to whether this will be implemented and when, but we will send it to our developers for consideration
