简体   繁体   English

SVN:对活动服务器进行版本控制的最佳实践?

[英]SVN: best practice for versioning you live server?

I want to track all changes on a Typo3 live server via SVN. 我想通过SVN跟踪Typo3实时服务器上的所有更改。 This works well so far but since I've updated an extention with the build in extention manager, I'm getting a SVN error: 到目前为止,此方法运行良好,但是由于我已使用构建扩展管理器更新了扩展,因此出现SVN错误:

svn: 'ext/realurl' is not a working copy directory

This is because the folder was replaced compleatly by the update process. 这是因为该文件夹已被更新过程完全替换。 Are there any best practices to handle such changes? 是否有最佳实践来应对此类变化? Would GIT be a better fit for such a scenario? GIT是否更适合这种情况?

Any help is highly appreciated. 非常感谢您的帮助。

It's because the Extension Manager deletes the existing extension folder and replaces it with the newer one. 这是因为扩展管理器删除了现有的扩展文件夹,并将其替换为较新的扩展文件夹。 That means, your ".svn" directories get deleted. 这意味着您的“ .svn”目录将被删除。

Best practice is to first do your Updates (better all your File-Changes) manually in a testing enviroment, commit the changes and then do a SVN-Update on your Live Server. 最佳实践是首先在测试环境中手动进行更新(最好进行所有文件更改),提交更改,然后在Live Server上进行SVN更新。

If this directory is a sub-folder of your working copy , you may simply use Subversion > v1.7. 如果此目录是工作副本子文件夹 ,则可以简单地使用Subversion> v1.7。

This way, subversion will store only one .svn folder at the top of the working copy (instead of one in each folder) , so even if subfolder is re-created, SVN will not send an error. 这样,subversion只会在工作副本的顶部存储一个.svn文件夹(而不是每个文件夹中的一个),因此,即使重新创建了子文件夹,SVN也不会发送错误。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM