I use the NetBeans IDE for editing PHP, HTML and CSS, and I keep all project files in a Subversion repo. I implement strict access controls for any other developers accessing projects, especially if they are consultants outside my company.This way I can prevent developers from changing (or even reading) parts of the source tree they're not authorized to and everyone working on the project can easily merge changes in with the work they are doing.
Trac is a vital part of my workflow as well, as it shows me what in the svn repo was changed, when, and why. Any changes to a project must have a trac ticket explaining what was to be changed, who requested it, and why; every SVN commit must have a trac number associated with it.
What I do is, when code is checked in to the development server using svn commit, a working copy on the development server is updated. That way, all testing is done via the webserver running on the development machine, allowing me to grant fine-grained access to developers -- they don't need all they code because they run and test their changes off my server. So the workflow for me is as follows:
Check Trac for a ticket describing work to be done
Update/Checkout code from svn to make sure I have the latest copy
Make changes to code/html/css in NetBeans
Commit changes to subversion. Staging site is automatically updated upon commit.
Test site off staging server. If more work needs to be done, go to 3.
When issue has been resolved, comment in Trac which SVN revisions I believed solved the issue and mark the ticket as ready for review
When client/management/etc approves ticket is completed, Trac ticket is closed.
发布评论
评论（6）
sh是我的IDE。您可以从那里执行任何操作：vim或emacs编辑文件git或其他一些 SCM，最好是分布式的）shis my ide. You can do anything from there:vimoremacsgitor some other SCM, preferably distributed)另一个很棒的 IDE 是 NetBeans，它应该满足您的所有需求：
Another great IDE is NetBeans which should fit all your needs:
您可以尝试使用 Eclipse 作为 IDE，使用插件来满足您的需求。
You might try Eclipse for the IDE using plugins to suite your needs.
一个好的语法高亮代码编辑器是一个巨大的帮助。
我的大部分开发工作都使用：
可配置的语法突出显示和有限的智能感知
多种语言和项目结构支持）
服务器管理工作室/Express(SQL
服务器）
A good syntax highlighting code-editor is a huge help.
I do most of my development using:
configurable syntax highlighting and limited intellisense for
multiple languages and project structure support)
Server Management Studio/Express(SQL
Server)
Coda 在一个窗口中很好地完成了许多重要的事情。
Coda does many important things very well, all in a single window.
重复使用我对另一个问题的回答 ：
我使用 NetBeans IDE 编辑 PHP、HTML 和 CSS，并将所有项目文件保存在 Subversion 存储库。我实施 严格对任何其他访问项目的开发人员进行访问控制，特别是如果他们是我公司外部的顾问。这样我就可以防止开发人员更改（甚至读取）他们无权访问的源代码树的部分以及每个人都在处理的内容项目可以轻松地将更改合并到他们正在做的工作中。
Trac 也是我工作流程的重要组成部分，因为它向我展示了 svn 存储库中的更改内容，何时以及为何。对项目的任何更改都必须有一份跟踪单，解释要更改的内容、请求者以及原因；每个 SVN 提交都必须有一个与其关联的跟踪号。
我所做的是，当使用 svn commit 将代码签入到开发服务器时，开发服务器上的工作副本会被更新。这样，所有测试都是通过在开发计算机上运行的网络服务器完成的，允许我向开发人员授予细粒度的访问权限——他们不需要所有代码，因为他们在我的服务器上运行和测试他们的更改。因此，我的工作流程如下：
To re-use much of my answer to a different question:
I use the NetBeans IDE for editing PHP, HTML and CSS, and I keep all project files in a Subversion repo. I implement strict access controls for any other developers accessing projects, especially if they are consultants outside my company.This way I can prevent developers from changing (or even reading) parts of the source tree they're not authorized to and everyone working on the project can easily merge changes in with the work they are doing.
Trac is a vital part of my workflow as well, as it shows me what in the svn repo was changed, when, and why. Any changes to a project must have a trac ticket explaining what was to be changed, who requested it, and why; every SVN commit must have a trac number associated with it.
What I do is, when code is checked in to the development server using
svn commit, a working copy on the development server is updated. That way, all testing is done via the webserver running on the development machine, allowing me to grant fine-grained access to developers -- they don't need all they code because they run and test their changes off my server. So the workflow for me is as follows: