In my previous posts, we went over the deployment process in the Optimizely/EpiServer DXP environment. The first and the second post of the Deployment API series went through the original methods that allow for deployment into the DXP environment. Smooth Deploy is a feature that I have been looking forward to for a long time […]
As of Update 357, Optimizely (EpiServer) released Direct Deploy into their Deployment API. This update allows major speed improvements when deploying into the integration environment.
In my previous posts, we went over the deployment process in the EpiServer DXP environment. The first and the second post of the Deployment API series went through the original methods that allow for deployment into the DXP environment. Smooth Deploy is a feature that I have been looking forward to for a long time now.
In my previous posts, we went over the deployment process in the EpiServer DXP environment. The first post went through the original methods that allow for deployment into the DXP environment. The second post went through update 313, which was a massive deployment API update, as well as how to use the API to export an environmental database, and how to sync down environments.
In my last-post, we went over the deployment process in the EpiServer DXP environment. I mentioned that the next post would be related to using this within Azure DevOps, but I need to make a slight adjustment based on today's update. As of today (4/27/2020), EpiServer released their weekly update #313, which included a lot
In late-2019, EpiServer released one of their Beta programs, which would allow partners and developers the ability to control the DXP environment deployments via an API. There have been a few blog posts (like this one by Anders Wahlqvist) on how to use these APIs in one-off instances, but none in how to make these
