简体繁体 English

如何正确部署DNN 9

[英]How to properly deploy a DNN 9

原文 2018-01-12 07:12:27 9 2 asp.net/ dotnetnuke/ dotnetnuke-9/ dnn-module

I'm developing a new internal company portal, and i'm using DNN 9 as a base CMS. 我正在开发一个新的内部公司门户网站，我正在使用DNN 9作为基础CMS。 Now that i have developed some modules, customize (layouts and icons, no core modifications) DNN to my liking. 现在我已经开发了一些模块，根据自己的喜好定制（布局和图标，没有核心修改）DNN。

How do i deploy DNN application from my dev environment to a production? 如何将DNN应用程序从我的开发环境部署到生产环境？ Would copy-paste the entire site and backup restore DB work? 是否会复制粘贴整个站点并备份还原DB工作？

2 个解决方案

Copy-paste/backup-restore would be the simplest approach for deploying your DNN site out to production. 复制粘贴/备份恢复将是将DNN网站部署到生产环境的最简单方法。

A couple of things to keep in mind. 要记住几件事。

1) Add the production URLs to the site before you put it in the wild, will make things easier. 1）在将生产URL放入野外之前将其添加到站点，这将使事情变得更容易。 2) Once you deploy, you really can't maintain both environments easily. 2）部署完成后，您实际上无法轻松维护这两种环境。 Changes made in one, will NOT be made in another. 在一个中进行的更改不会在另一个中进行。 3) If you're making changes to "modules" that you've built, you would typically start packaging and deploying (install/upgrade) those, hopefully you used my VS templates, if so that part is super easy. 3）如果你正在对你构建的“模块”进行更改，你通常会开始打包和部署（安装/升级）那些，希望你使用我的VS模板，如果是这样，那部分非常简单。

You could deploy from DEV to PROD again, but any changes you make in prod will be lost by the process, that's why I say #2 isn't easy. 您可以再次从DEV部署到PROD，但是您在prod中所做的任何更改都将被进程丢失，这就是为什么我说＃2并不容易。

Chris' comments are spot on. 克里斯的评论很明显。

You might want to consider using Evotiva's DNN Backup and Restore product to simplify the process. 您可能需要考虑使用Evotiva的DNN备份和还原产品来简化该过程。