小型办公室处理文件的最佳方式是什么？
我目前在一家小型网络开发公司工作，我们主要做活动网站和其他促销活动。 第一年，我们一直使用“服务器”来共享项目文件，这是一台具有网络共享功能的普通 Windows 机器。 但这并不完全是未来的证明。
SVN 非常适合代码（这就是我们现在使用的），但我希望对所有或大部分文件进行版本控制（或至少某种形式的同步）。
我本质上想要的是像 subversion 对代码所做的那样，但对我们的文档/psd/pdf 文件。
我意识到 subversion 也可以处理二进制文件，但我觉得这对我们来说可能有点过分了目的。 它不一定需要完整版本控制系统的所有功能，但可以消除增量命名（Notes_1.23.doc）的需要，并减少错误覆盖某些内容的机会。
它还需要是多平台的，可以处理大文件（100 mb 以上）并且可供非技术人员使用。
I'm currently working at a small web development company, we mostly do campaign sites and other promotional stuff. For our first year we've been using a "server" for sharing project files, a plain windows machine with a network share. But this isn't exactly future proof.
SVN is great for code (it's what we use now), but I want to have the comfort of versioning (or atleast some form of syncing) for all or most of our files.
What I essentially want is something that does what subversion does for code, but for our documents/psd/pdf files.
I realize subversion handles binary files too, but I feel it might be a bit overkill for our purposes.
It doesn't necessarily need all the bells and whistles of a full version control system, but something that that removes the need for incremental naming (Notes_1.23.doc) and lessens the chance of overwriting something by mistake.
It also needs to be multiplatform, handle large files (100 mb+) and be usable by somewhat non technical people.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
SVN 也非常适合二进制文件。 如果您担心无法比较修订版本，我可以告诉您，使用 Tortoise 对于 Word 文档是可能的。
但我不知道“扩展版本控制”是什么意思。 SVN 不是文档管理系统。
编辑：
如果您已经在使用 SVN 并且它满足了您的目的，为什么还要费心使用第二个系统呢？
SVN is great for binaries, too. If you're afraid you can't compare revisions, I can tell you that it is possible for Word docs, using Tortoise.
But I do not know, what you mean with "expanding the versioning". SVN is no document management system.
Edit:
If you are already using SVN and it fulfils your purposes, why bother with a second system?
我们刚刚转移到 Perforce 并且对此非常满意。 它是一款商业产品，但功能强大且易于使用，恕我直言，它值得每个座位的价格。
We've just moved over to Perforce and have been really happy with it. It's a commercial product, but it's so powerful and easy to use that it's worth the price per seat IMHO.
一个合适的文件夹结构和命名方案？
VCS 并不能很好地处理图像等 - 是否可以将代码放在 VCS（SVN/Git/Mercurial 等）中，并为二进制资产（源照片、Photoshop PSD）提供合理的文件夹结构文件、Illustrator 文件等）？
它不能处理同步，但中央文件服务器可以实现同样的功能。
这需要一些强制措施和小猫聚集才能让人们正确命名，但我认为为每个资产都有一个版本文件夹（如 someproject/asset/header_logo/v01/header_logo_v01.psd）基本上就像 VCS，但更容易在不同版本之间移动（当客户决定他们更喜欢 v02 而不是 v03 时，没有
vcs checkout blah -r 234）A decent folder structure and naming scheme?
VCS don't really handle images and such very well - would it be possible to have the code in a VCS (SVN/Git/Mercurial etc), along-side a sensible folder structure for the binary-assets (source photos, Photoshop PSD files, Illustrator files and so on)?
It wouldn't handle syncing, but a central file-server would achieve the same thing.
It would require some enforcing and kitten-herding to get people to name things properly, but I think having a version folder for each asset (like someproject/asset/header_logo/v01/header_logo_v01.psd) will basically be like a VCS, but easier to move between different revisions (no
vcs checkout blah -r 234when a client decides they prefered v02 more than v03)您的问题很有趣，因为您指定它适合小型办公室。 在企业级别，我会推荐类似于 EMC Documentum 的 eRoom，但显然这将远远超出您的需要，并且在成本方面也超出您的期望。 我不确定这方面的许可细节，但我听说如果您的办公室有 MS Office，您就可以访问 Sharepoint，这可能很适合您。 我也确信有很多此类东西的 SAAS 实现，所以你可能需要查看一下，请记住服务器不会由您托管，因此如果材料极其敏感，那显然不是正确的路线。
Your question is interesting because your specifying that it be suitable for a small office. At the enterprise level, I would recommend something along the line of EMC Documentum's eRoom, but obviously thats going to be way more than you need, and more than you want cost-wise as well. I'm not sure of the licensing details on this but I've heard that if your office has MS Office, you have access to Sharepoint, which might work well for you. I'm also sure there are a lot of SAAS implementations of this kind of stuff, so you may want to look at that, keeping in mind that the servers will not be hosted by you, so if the material is extremely sensitive, thats obviously not the proper route.
Windows Vista 在其文件系统中具有本地文件版本控制功能，这可能很有用，但在团队合作方面受到限制。 但是，如果有人覆盖了其他人的文件，则会按原样存储新版本。
Windows Vista features local file versioning in its file system, which can be useful, but is limited in terms of teamwork. However, if somebody overwrites somebody else's file, a new version is stored as it should be.
还要考虑知识树。 看看它，一些演示/屏幕截图可以在
http://www.knowledgetree.com/
它有一个免费的开源社区版 - 因此具有成本效益。 我们还没有尝试过，但对于寻求文档版本控制解决方案的小型企业，我们选择了这个系统而不是其他系统。
Also consider KnowledgeTree. Have a look at it, some demos/screenshots are available at
http://www.knowledgetree.com/
It has a free open source Community Edition - so it's cost effective. We haven't tried it, but we chose this one over other systems for a small business looking for document versioning solution.
您可能需要考虑使用 Mac 作为服务器，并使用 Time Machine 来备份您的共享文件夹。 这样做可以自动备份并允许您通过 Samba 共享，以便每个人都可以拥有网络驱动器在他们的计算机上。 Mac 服务器可能有点大材小用了。 Mac Mini 适合小型办公室或改造后的台式机。
您还可以考虑使用 Amazon 的 S3 服务 进行离线备份。 由于它是一种即用即付的服务，因此可以根据使用情况进行扩展，如果您觉得想要转移到其他地方，您可以随时下载数据并将其带到其他地方。
You might want to consider using a Mac as your server and using Time Machine to backup your shared folders. Doing this gives you automatic backups and allows you to share through Samba so everyone can have a network drive on their computer. A Mac server is probably overkill. A Mac Mini would do for a small office or a repurposed desktop machine.
You might also consider Amazon's S3 service to do offline backups. Since it's a pay-as-you-go service this can scale with use, and if you feel you want to move to something else you can always download your data and take it somewhere else.
如果您有 Windows 2003 服务器，则可以查看 Sharepoint Services 3.0 (http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb684453.aspx）。
它可以对文档进行版本控制，并且与Office有很好的集成，从Office xp开始，但office 2003和2007更好。 Office 和 PDF 文件可以被索引（通过 Adobe IFilter）和搜索。 您还可以添加 IFilter 来搜索文档中的元数据。
对于大文件，默认最大文件大小为 50MB，但可以配置。
If you have a windows 2003 server, you can have a look at Sharepoint Services 3.0 (http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb684453.aspx).
It can do version control for documents, and has a nice integration with Office, starting with Office xp, but office 2003 and 2007 are better. Office and PDF files can be indexed (via Adobe IFilter), and searched. You can also add IFilters to search metadata in your documents.
Regarding large files, by default the max filesize is 50MB, but it can be configured.