如何在团队环境中使用通用开发服务器来使用Coldfusion Builder 2？ [英] How do you use Coldfusion Builder 2 in a team environment using a common development server?
问题描述
我们的CF 9开发环境是在一个通用的开发服务器（DEVWEB）上。我们正在寻找从Dreamweaver移动到Coldfusion Builder作为我们的IDE，我担心CF Builder在项目根目录中删除.settings目录和.project文件的方式。
开发团队如何处理这个问题？如果团队成员更改了他们的设置，他们对项目首选项/设置的更改是否覆盖了我的？
我们希望不要在本地安装的CF上进行工作
感谢您的帮助/建议！
当你说普通服务器时，我假设你的意思是每个人都有文件共享访问代码并进行更改。我们曾经这样做，但我们解决了我们的问题与以下：
- subversion源计数。所有代码都进入存储库。 GIT也是一个很好的解决方案。
- 本地工作站开发。每个开发人员都有一个代码和CF / Web服务器在其本地Win7或MAC上运行的副本。他们进行更改并将代码提交到存储库。
- Hudson持续集成服务器。此产品允许我们创建一个部署脚本，从我们的SVN更新我们的共同开发服务器。
- 提交后钩子/触发器。有了一个小脚本，我们的SVN提交可以触发哈德逊来运行我们的共同服务器上的构建。
结果是非常相似的到整个团队在单个服务器上开发，因为每个源代码控制提交导致该代码被推送到公共服务器（我们称为分段服务器）。
因为SVN或GIT有很好的集成eclipse工具，源代码控制部分（有时看起来像最难的）实际上是最容易习惯的。
最困难的部分通常是开发人员必须在其本地工作站上运行Web服务器/ CF服务器，这可能或可能不是由它和许多开发者太多:)不了解底层的web / cf技术，所以他们有一些东西要学习...像如何设置一个数据源，添加一些类路径或创建一个虚拟目录在apache或IIS 。但这些课程一般会提高你的员工的调试技能 - 所以这是一个胜利。
当你完成后，你有几件事情，你以前没有 - 源控制，持续集成，新技能等。所有这些都将有利于你的员工整体。这是我的想法 - 如果你想要更多的细节，请随时与我联系。
Our CF 9 development environment is on a common development server (DEVWEB). We're looking at moving from Dreamweaver to Coldfusion Builder as our IDE and I'm concerned about the way CF Builder drops a .settings directory and .project file in the root of the project.
How do development teams deal with this? If a team member make changes to their settings, don't their changes to the project preferences / settings overwrite mine? Or are the types of settings that are included in those bundles the types of things that SHOULD be propagated among team members?
We would prefer NOT to work on local installations of CF for development.
Thanks for any help / suggestions with this!
Chris
Chris, when you say common server I assume you mean that everyone has file share access to the code and makes changes. We used to do it that way but we solved our problem with the following:
- subversion source countrol. All code goes into a repository. GIT is also a good solution.
- Local workstation development. Each developer has a copy of the code and CF/Web server running on their local Win7 or MAC. They make changes and "commit" the code to the repository.
- Hudson continuous integration server. This product allows us to create a deployment script that updates our common development server FROM our SVN.
- Post commit hooks/triggers. With a little scripting our SVN commits can "trigger" hudson to run a build onto our common server.
The result is something very similar to the whole team developing on a single server because each source control commit results in that code being pushed to the common server (which we call a "staging" server).
since SVN or GIT have great integrated eclipse tools the source control part of this (which sometimes seems like the hardest) is actually the easiest to get used to.
The hardest part is usually that developers have to run a web server/CF server on their local workstation which may or may not be up to it - and many devs (way too many :) don't know anything about the underlying web/cf technology so they have a few things to learn... like how to set up a datasource, add something to a class path or create a virtual directory in apache or IIS. But these lessons generally enhance the debugging skills of your staff - so it's a win.
When you are done you have several things that you did not have before - source control, continuous integration, new skills etc. All of which will benefit your staff overall. That's my take - feel free to contact me off line if you want more details.
这篇关于如何在团队环境中使用通用开发服务器来使用Coldfusion Builder 2？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
