如何将现有的 Sitecore 6.2 站点部署到新环境?

发布于 2024-10-07 21:02:08 字数 326 浏览 0 评论 0原文

我想部署一个我一直在使用的 Sitecore 测试站点,从单一开发人员平台(一切都在一台本地 PC 上)到更像测试环境(专用 IIS 和 SQL 服务器、对 IIS 的虚拟访问)。我现在确实不需要太担心团队开发和源代码控制,尽管开发将在本地继续,并将包部署到测试环境。

是否有执行此操作的最佳实践文档?

我可以简单地在 IIS 上安装一个空的 Sitecore 实例,然后复制所有内容(编辑连接字符串以指向正确的数据库等)吗?如果是这样,最好使用安装程序或 zip 文件?

除了确保正确的服务器配置(.NET 版本、安全设置等)之外,还有什么我应该特别注意的吗?

提前致谢。

I want to deploy a Sitecore test site I've been playing with from a single developer platform (everything on one local PC) to something more like a test environment (dedicated IIS and SQL servers, virtual access to IIS). I don't really need to worry too much about team development and source control right now, though development will continue locally with packages deployed to the test environment.

Is there any best practice documentation for doing this?

Can I simply install an empty Sitecore instance on the IIS and then copy everything over (editing connection strings to point to correct DBs etc)? If so it best to use the installer or the zip file?

Aside from ensuring correct server configuration (.NET version, security settings etc) is there anything I should be paying particular attention to?

Thanks in advance.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

咆哮 2024-10-14 21:02:08

幸运的是,移动 Sitecore 安装是一项相当简单的任务,并且您可以使用多种方法。这是我通常会做的(稍微简化)。

  • 设置目标环境。含义 IIS、SQL Server、安全设置等
  • 分离我的本地数据库,停止本地 IIS
  • 将根解决方案文件夹中的所有内容复制到目标环境
  • 将数据库附加到目标 SQL 服务器
  • 创建 IIS 网站,并将其指向到您的网站文件夹
  • 修改 ConnectionStrings.config
  • 修改数据文件夹的绝对路径
  • 按 GO!

是否要使用 Sitecore Installler 取决于个人喜好。它确实为您设置了很多配置问题,但我个人从不使用它。我选择“Zip of the root”。

我认为我无法列出您应该特别注意的事项的完整列表,但这里有一些最常见的事项

  • 测试环境应尽可能类似于实时环境,因此请将您的 /data 文件夹移到外部网络根目录。您不希望人们只需输入 website/data/license.xml 即可下载您的许可证文件;-)
  • 考虑创建一个 .config 包含文件 用于您的计算机特定设置(即邮件服务器、外部组件等)
  • 持续(呃...)集成周期,开始部署更新通过 packages 到目标,以便您积累管理最终实时环境的生命周期经验
  • 确保保持相同的 Sitecore 版本 跨您的环境
  • 不要太担心;-) Sitecore 虽然范围广泛,但从部署角度来看是一个“简单”的 ASP.NET 应用程序。

希望这能提供一些见解:-)

Fortunately, moving a Sitecore installation around is a fairly simple task, and there are a number of approaches you could be using. Here's what I would normally do (somewhat simplified).

  • Set the target environment up. Meaning IIS, SQL Server, security settings and so on
  • Detach my local databases, stop the local IIS
  • Copy everything from the root solution folder and down, to the target environment
  • Attach the databases to the target SQL server
  • Create the IIS website, and point it to your Website folder
  • Modify ConnectionStrings.config
  • Modify your absolute path to your data folder
  • Press GO!

Whether you want to use Sitecore Installler or not is a matter of personal preference. It does set a lot of configuration issues for you, but personally I never use it. I go with "Zip of the root".

I don't think I could come up with a full list of things you should be paying particular attention to, but here's a few of the most common ones

  • Test environments should resemble live as much as possible, so do move your /data folder outside the webroot. You don't want people to be able to download your license file by simply typing website/data/license.xml ;-)
  • Consider creating a .config include file for your machine specific settings (i.e. mail servers, external components and so on)
  • Start on a continueous (erm...) integration cycle, start deploying your updates via packages to the target so you work up experience on lifecycle managing your eventual live environment
  • Make sure you keep the same Sitecore version across your environments
  • And don't worry too much ;-) Sitecore, although extensive, is a "simple" ASP.NET application from a deployment perspective.

Hope this provides a bit of insight :-)

眼泪都笑了 2024-10-14 21:02:08

关于安装程序与 Zip,我一直更喜欢 zip。

它看起来更快,我可以控制整个过程......加上我玩过的第一个安装程序似乎从来没有工作得那么好或根本没有工作。

关于移动站点,我建议制作一个解决方案的清理压缩包。

有些东西是不需要的,通常这些东西是不需要的:

viewstate文件夹内容
诊断文件夹内容
MediaCache 文件夹内容
审核文件夹内容
临时文件夹内容
索引文件夹内容

,但通常您需要这些文件夹,而不是内容,例如 MediaCache 文件夹,它是在从数据库检索媒体项目时由 Sitecore 生成的。

With regards to Installer vs Zip I've always prefered the zip.

It seems faster and I get to control the whole process... plus the first installers I played with never seemed to work that well or at all.

With regards to moving a site, I'd say make a cleaned up zip of the solution.

there are things that are not needed, usually these things are not needed:

viewstate folder content
diagnostics folder content
MediaCache folder content
audit folder content
temp folder content
indexes folder content

but usually you need these folders, just not the content, as for instance with the MediaCache folder, it's generated by Sitecore when media items are retrieved from the database.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文