Hi
Do you have any recomendations/best practices to how we can automate deployment solutions by CI/CD?
//Mads
Hi
Do you have any recomendations/best practices to how we can automate deployment solutions by CI/CD?
//Mads
Hi Mads
We do not have a best practice of how to do or automate deployments - everyone has their own combination of development tools and environments, so that would not be usable for many.
Dynamicweb has a built-in deployment tool that can be used to move Dynamicweb specific data like settings, ecommerce setup, content, item types, files etc from you local development machine onto staging/live environments - check out the docs here: https://doc.dynamicweb.com/documentation-9/platform/platform-tools/deployment-tool
Dynamicweb is 'just' another asp.net application with a database - so you can use any deployment tools and policy that can work with an ASP.NET and SQL-Server based application for deployment of you custom code and templates (templates can also be deployed using the Dynamicweb deployment tool)
If you are using Visual Studio, you can configure web-deploy - that is what we use internally: https://docs.microsoft.com/en-us/visualstudio/deployment/deploy-iis-with-web-deploy?view=vs-2017
Also Microsoft have a number of ways of deploying databases, i.e. https://msdn.microsoft.com/en-us/library/dd465343(v=vs.100).aspx
Hope this gives you some pointers.
BR Nicolai
Hi Nicolai
How are you using it along with the upgrade strategy (https://doc.dynamicweb.com/get-started/introduction/installation/upgrading-dynamicweb), do you only publish the files folder via webdeploy or...?
Hi Mads
Yes, only /Files and your custom dlls. NOT Dynamicweb
BR Nicolai
Hi Nicolai
What if we use nuget to install, would you still only publish /files and dlls or the whole project?
Depends... I do not like to use web deploy for updating the entire Admin to production. But of course you can do it.
Personally I would put the copy of the new Dynamicweb in place on the server (it is a lot file copying) and then make the switch either in IIS or by renaming the old/new folders. It will result in a much shorter downtime and less risk.
Also when using webdeploy you risk to have dlls that you deleted and do not want anymore etc.
BR Nicolai
You must be logged in to post in the forum