Is Git just for source control?

Question

Is it any wonder to integrate Git into a project that has nothing to do with version control.

I think of a data collector that regularly runs several client-side commands and passes the output to the local Git repository. If a remote server is available, it pushes the source data for further processing on the server side. In this case, I will have free compression, history and various delivery methods. What are the disadvantages?

Answer 1

This is not crazy, no. Git was originally intended only for a managed version of the file system, which will subsequently be used as the basis for a version control system; however, this is not entirely true, and Git has become the original management system. However, this is still a very large file system design, and there is no reason why you could not use it for other purposes (in fact, I was going to do something very similar to myself, but the project never left system).

Answer 2

It depends on what data you want to process. If you are talking about small bits of data, use a database instead, but if you want to track changes in documents, then I don’t see a problem creating your system on top of something like Git.

Answer 3

Several Git-based backup systems already exist, such as Gibak . Thus, it is definitely capable of efficiently processing large data sets.

The downside is that you cannot combine binary data.

Answer 4

"Git is a free and open distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Each Git clone is a complete repository with a complete history and full change tracking capabilities, independent of network access or a central server. Branching and merging are quick and easy.

Git is used for versioning files like tools like Mercurial, Bazaar, Subversion, CVS, Perforce, and Visual SourceSafe. "

Answer 5

It would be easier for me to collect data in a database. The information in the database is organized, easily accessible and can be easily manipulated. Also, if you need remotely accessible to people, allow other domains access to the database.

While in Git you are stuck storing everything in flatfiles. It is your job to parse all this information, and if you have a lot of information, it can take a lot of time. However, databases tend to return the exact information you want pretty quickly.

Answer 6

It looks like what you are looking for is a message queue or service bus. There are many of those. Of course, if Git works for you, why not? But just make sure that you are not just using it, because it is the only tool that you know.

Answer 7

I don’t see how this would be a bad idea. Git is great for managing large and small amounts of information. Binary or text files are allowed and stored in the change history.

It may work like iFolder , but with a much better ability to merge, keep a story and share its information.

One problem is the complexity overriding this type of setup. If your users are not well versed in branching, wswwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww.

The idea of ​​a GUID will also be confused with end users, so you may need to create something simple (version numbering). Non-empty folders resolving the dilemma must also be addressed.

The good thing about git (unlike svn or iFolder) is that moving a file is easy and merging is smart.

All in all, git works great with our binary image, media and code files in one repository. I cannot think of why it cannot be used as an assistant for any other project to track documents, images, and other media.

Answer 8

I use Subversion to backup the database. One line per record with many static entries makes svn a quick and easy backup solution. There are no significant flaws that I see. From one random internet guy to another: you have my support!

Answer 9

not only for source control.

people use it as a version control system for all kinds of documents, such as manuscripts, speeches, etc.

git doesn't need to be used with source control software, you can use it, but you want to