Manage documents with GIT

I am working on a website where I can create a project and upload data to each of my products. Data can be mainly in the form of spreadsheet documents, images, PDF files, etc. Ideally, I would like to use the VCS (git pref) setup type, where every time I update a specific document, I could just pass that document to the repo. Any ideas on how I can implement would be helpful.

+5
source share
3 answers

You can invoke git in a subshell after each boot.

But I don’t think that using any VCS is a good solution for version control of documents, especially in a web application. This is due to the fact that with office documents you will use mainly binary data. VCS sucks (without exception) when it comes to binary data. You won’t be able to make any differences, and metadata management is not suitable for such things - the author of the commit is mostly limited to a specific account (and you will probably use one system account for git), no additional information (except information on the basic file: size, permissions, ctime) is saved, so you have to store it (authorship, permissions for web application users, additional metadata) near you. Also note that multiple users can simultaneously transmit data,therefore, there will be branches in your version control. When you have a huge data set (and with binary office files, it may appear faster than you think), you will not be able to split such a repository.

IMO, VCS, .

( , , ) . . : , . - .

+8

( , )

- , ( 'git add -A && git commit -m "xxx" Git) 5 , .

, Mark Longair :

flashbake cron, , , - .
, , .

:

  • , , .
  • , , .
  • = > .
+1

As a response from Cezio's answer, if you really want to use VCS for version control, consider LaTeX. Since this is essentially the source code that is compiled into a document (usually PDF via pdflatex), it is a reasonable candidate for version control.

+1
source

All Articles