如何设置 SVN 来进行一般网站开发/部署？
这适用于一般网站开发（LAMP Stack），但不一定是 Web 应用程序。
我只是想为正在构建的客户端网站设置一些版本控制。只是想找出最好的方法 - 以及如何做到这一点...
我不知道如何在我的服务器上设置 SVN。我是否需要执行额外的步骤才能将主干中的内容推送到域使用的目录？
菜鸟警报：我知道我想做什么，但如果我没有提供足够的细节，请告诉我，我会更新..
This is for general websites development (LAMP Stack), not necessarily web applications though.
I'm just trying to setup some version control for client websites im building. Just trying to figure out the best way -- well how to do this...
I don't know how to setup SVN on my server. Do I have to do an additional step to push what's in trunk to the directory that the domain uses?
Noob alert: I have an idea of what Im trying to do but if I'm not giving enough details let me know I'll update..
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我将开发和生产环境分开；也就是说，服务器从不使用工作副本。
编辑以澄清：“服务器从不使用工作副本”是指“svn checkout”永远不会在服务器上执行，因此服务器上没有 WC。相反，“svn export”命令可以用来“拉出修订版本”，而无需创建 WC。
然而，有时很容易将（特定的测试标签）拉到服务器上。所以，作为一种传输机制，SVN 有时很方便。
I keep development and production environments separate; that is, the server never uses a working copy.
Edit for clarification: By "sever never uses a working copy" I mean that the "svn checkout" is never executed on the server and thus there is no WC located on the server. Instead the "svn export" command can used to "pull a revision" without creating a WC.
However, sometimes it is easy to pull (a specific tested tag) onto a server. So, as a transport mechanism, SVN is sometimes handy.
不。您应该构建 WAR 文件，可能将其保存到 Maven 存储库之类的文件中，然后部署它。现在 - 我正在谈论 J2EE 我真的不知道您想到的是哪种技术。但无论如何 - SVN 适用于您的源代码和资源，而不是可执行代码。另外 - trunk 用于您的最新代码（开发），您可能想为生产部署创建一个发布分支
。灯。我仍然会使用某种发布方式将文件从 SVN 移动到您想要部署的任何位置。 Ant、Maven——类似的东西。将 SVN 存储库映射到 Web 服务器通常不是一个好主意，您希望将发行版和源代码分开。表示 - 文件夹结构可以相同
No. You should build WAR file, probably save it into something like Maven repo and then deploy that. Now - I'm talking J2EE I don't really know which technology you have in mind. But anyway - SVN is for your source code and resources, not for executable code. Plus - trunk is for your latest code (development) you probably want to create a release branch for production deployment
OK. LAMP. I would still use some sort of publishing to move files from SVN to wherever you want to deploy it. Ant, Maven - something like that. It's generally not a good idea to map your SVN repo to your webserver, you want to keep distro and source separate. Said that - the folder structure can be identical