适合许多开发人员的 php、zend 调试、svn 设置
我正在尝试为许多用户创建一个环境来开发许多 php 项目。
我已经在 Windows 2003 服务器上安装了 Zend 服务器社区版。 我已经共享了 apache/htdocs 文件夹。
每个用户在 htdocs 中有一个自己的文件夹，说：
/htdocs/bob/
/htdocs/sarah/
/htdocs/michael/
...
对于他们在文件夹中正在处理的项目，说：
/bob/accountingSoftware/
/bob/eCommerceSite/
/bob/newCMS/
...
在该项目文件夹中，他们将有一个 svn 签出，说：
/accountingSoftware/trunk/
/accountingSoftware/tag/
/accountingSoftware/branch/
这很好用，但是 svn 现在非常慢，因为它在网络驱动器上工作。谁能提出解决方案？
我计划让每个开发人员使用 Eclipse，并利用 Zend 服务器调试功能。但我不清楚如何做到这一点，我的设置适合吗？
我目前只与一些开发人员测试此设置，因此我更愿意现在进行任何重大的结构更改/改进。
如果有任何意见或建议，我将不胜感激。
提前致谢。
I'm trying to create an environment for many users to develop many php projects on.
I've installed Zend server community edition on a Windows 2003 server.
I've shared the apache/htdocs folder.
Each user has a their own folder in htdocs, say:
/htdocs/bob/
/htdocs/sarah/
/htdocs/michael/
...
With the projects they are working on in their folder, say:
/bob/accountingSoftware/
/bob/eCommerceSite/
/bob/newCMS/
...
Within that project folder they will have an svn checkout, say:
/accountingSoftware/trunk/
/accountingSoftware/tag/
/accountingSoftware/branch/
This works well, however svn is now incredibly slow because it's working on a network drive. Can anyone suggest a solution to this?
I'm planning on getting each developer to use Eclipse, and take advantage of the Zend server debugging features. But I'm not clear on how to do this, is my setup appropriate for this?
I'm only testing this setup with a few developers at the moment, so I'd prefer to make any big structural changes/improvements now.
I'd appreciate any comments or suggestions.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我建议在每个开发人员的计算机上安装本地 Zend 服务器，并让共享服务器运行当前的主干代码。
这允许每个开发人员在需要时重新启动服务器，并允许他们在本地工作而不必担心网络驱动器。
它还允许您拥有一个共享位置，可以运行每个人的最新代码，而不必担心每个用户部分完成的更改。
如果您尝试让所有开发人员在一台服务器上工作，那么您总会有一些您无法支持的开发人员。通过让每个人都在本地工作，您可以拥有所需数量的开发人员。
I would recommend installing a local Zend server on each developer's computer and have your shared server be running the current trunk code.
This allows each developer to restart the server when they need, and allows them to work locally and not worry about a network drive.
It also allows you to have a shared location where the latest code from everyone can be run without worrying about partially completed changes from each user.
If you try to have all your developers working on a single server, you will always have some number of developers that you cannot support. By having everyone work locally, you can have as many developers as you need.