如何使用托管内容来管理应用程序 [英] How do you CM an application with managed content

问题描述

我们有一个网络应用程序，其中包含一系列内容，系统操作员可以更改（例如新闻和事件）。有时我们发布新版本的软件。该软件被标记和存储在subversion。但是，我有点被撕毁如何最好的版本控制可以独立更改的内容。什么是人们使用的一些机制，以确保内容存储和版本控制的网站可以重新创建或至少版本控制？

解决方案

当你确定两组文件有自己的生命周期（软件文件在一边，新闻和事件在另一方面，你知道：

$

您不能将同一个标签

/ ul>

您需要单独保存新闻和事件文件（在VCS中或在像Ian Jacobs建议的DB中，或在CMS - 内容管理系统中）并找到一种方法将链接到一起（一个id，一个时间戳，一个元标签，...）

不要忘记你不只是谈论两考虑在这个SO问题中引入的术语

href =http://stackoverflow.com/questions/438969>资产管理是源控制的超集由 S.Lott

• 软件文件：基础设施信息，即的企业信息资产。


• 新闻和事件：企业信息
/ strong>，即数据（不处理）;这通常在内容管理器和关系数据库之间分割。

因此，并非一切都会在Subversion中结束。

We have a web application which contains a bunch of content that the system operator can change (e.g. news and events). Occasionally we publish new versions of the software. The software is being tagged and stored in subversion. However, I'm a bit torn on how to best version control the content that may be changed independently. What are some mechanisms that people use to make sure that content is stored and versioned in a way that the site can be recreated or at the very least version controlled?

解决方案

When you identify two set of files which have their own life cycle (software files on one side, "news and events" on the other, you know that:

• you can not versionned them together at the same time
• you should not put the same label

You need to save the "news and event" files separatly (either in the VCS or in a DB like Ian Jacobs suggests, or in a CMS - Content Management system), and find a way to link the tow together (an id, a timestamp, a meta-label, ...)

Do not forget you are not only talking about two different set of files in term of life cycle, but also about different set of files in term of their very natures:

Consider the terminology introduced in this SO question "Is asset management a superset of source control" by S.Lott

• software files: Infrastructure information, that is "representing the processing of the enterprise information asset". Your code is part of that asset and is managed by a VCS (Version Control System), as part of the Configuration management discipline.
• "news and events": Enterprise Information, that is data (not processing); this is often split between Content Managers and Relational Databases.

So not everything should end up in Subversion.

这篇关于如何使用托管内容来管理应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！