I create websites for people. I have given them the ability to edit certain areas of their published pages using CushyCMS. That works fine, and everyone is happy with it.
我为人们创建网站。我已经让他们能够使用CushyCMS编辑他们发布的页面的某些区域。这很好,每个人都很满意。
When I go to publish some of my more extensive changes, I first need to pull down the latest version that they have produced. Then I make my changes, and upload everything to production.
当我发布一些更广泛的更改时,我首先需要下载他们生成的最新版本。然后我进行更改,并将所有内容上传到生产中。
I would like to use some sort of version control in this process. This should be a classic update-edit-commit-publish workflow, but I'm not sure how to go about this. Basically I want to avoid pulling down everything locally and doing the commits. I only want to pull down what has changed.
我想在这个过程中使用某种版本控制。这应该是一个经典的update-edit-commit-publish工作流程,但我不知道如何解决这个问题。基本上我想避免在本地删除所有内容并进行提交。我只想拉下变化的东西。
I use filezilla, and it doesn't do a good job of identifying changed files. I can't rely on the filesize, because sometimes it stays the same. I can't rely on timestamps because the server time is different than my machine, and it never seems to work correctly.
我使用filezilla,并没有很好地识别更改的文件。我不能依赖文件大小,因为有时它保持不变。我不能依赖时间戳,因为服务器时间不同于我的机器,它似乎永远不会正常工作。
How can I get around my problem? I use Notepad++, Subversion and FileZilla, but I'm willing to try other tools if they would make this process easier.
我怎样才能解决我的问题?我使用Notepad ++,Subversion和FileZilla,但我愿意尝试其他工具,如果他们能让这个过程更容易。
2 个解决方案
#1
It comes down to CushyCMS's decision to edit files directly and not put the user-provided content in a database like WordPress, DotNetDuke, Drupal, etc. So the real answer is you can't get there from here and should look into migrating to a database backed CMS. Thats not what you want to hear though.
它归结为CushyCMS决定直接编辑文件而不是将用户提供的内容放在像WordPress,DotNetDuke,Drupal等数据库中。所以真正的答案是你无法从这里到达那里并且应该考虑迁移到数据库支持的CMS。那不是你想听到的。
Version control will get you part of the way to concurrency but there is always the possibility of a user updating a page between your pull down and publishing the revised copy since your users wouldn't be checking into the version control system directly. That would require them to learn the version control system and negate the ease that CushyCMS (or any CMS really) provides. You'll want to try and find a system that allows your live site to be the Master to which you compare and check-out files from. I do not know of any mainstream systems that currently work that way.
版本控制将使您获得并发的一部分,但是用户在下拉和发布修订副本之间总是有可能更新页面,因为您的用户不会直接检入版本控制系统。这将要求他们学习版本控制系统并否定CushyCMS(或任何CMS真正提供)的易用性。您将要尝试找到一个系统,该系统允许您的实时站点成为您比较和检出文件的主站点。我不知道目前以这种方式工作的任何主流系统。
#2
I found that it was easiest to use a tool like Beyond Compare to handle the synchronization.
我发现使用Beyond Compare之类的工具来处理同步是最简单的。
#1
It comes down to CushyCMS's decision to edit files directly and not put the user-provided content in a database like WordPress, DotNetDuke, Drupal, etc. So the real answer is you can't get there from here and should look into migrating to a database backed CMS. Thats not what you want to hear though.
它归结为CushyCMS决定直接编辑文件而不是将用户提供的内容放在像WordPress,DotNetDuke,Drupal等数据库中。所以真正的答案是你无法从这里到达那里并且应该考虑迁移到数据库支持的CMS。那不是你想听到的。
Version control will get you part of the way to concurrency but there is always the possibility of a user updating a page between your pull down and publishing the revised copy since your users wouldn't be checking into the version control system directly. That would require them to learn the version control system and negate the ease that CushyCMS (or any CMS really) provides. You'll want to try and find a system that allows your live site to be the Master to which you compare and check-out files from. I do not know of any mainstream systems that currently work that way.
版本控制将使您获得并发的一部分,但是用户在下拉和发布修订副本之间总是有可能更新页面,因为您的用户不会直接检入版本控制系统。这将要求他们学习版本控制系统并否定CushyCMS(或任何CMS真正提供)的易用性。您将要尝试找到一个系统,该系统允许您的实时站点成为您比较和检出文件的主站点。我不知道目前以这种方式工作的任何主流系统。
#2
I found that it was easiest to use a tool like Beyond Compare to handle the synchronization.
我发现使用Beyond Compare之类的工具来处理同步是最简单的。