Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

best practice in storing non-source files under version control

I have a project under version control, but the project has some images, videos and zip files that change every so often. I don't want to store these files under version control because they take up a lot of space and make updates and commits very slow.

What's a good way of dealing with this issue and still commit non-source files that have changed? is there a better way?

I'm currently using subversion, if there is another version control client that is better for dealing with this issue, please recommend it!

like image 694
Charles Ma Avatar asked Jul 17 '09 05:07

Charles Ma


People also ask

What sort of file should not be put into a source code repository?

Config files with sensitive information (passwords, private keys etc.)

How version control is applied in the management of shared content?

Version control enables multiple people to simultaneously work on a single project. Each person edits his or her own copy of the files and chooses when to share those changes with the rest of the team. Thus, temporary or partial edits by one person do not interfere with another person's work.


1 Answers

I have lots of non-source files in SVN and the only time it slows down the commit is when I change them. I don't see how this is an issue if they're only changing "every so often". Also the size really shouldn't be a concern. If your repository is on a server and you're worried about how much space it's taking up you need to upgrade. Hard drives are cheap. Buy them.

Some people feel strongly that non-source files don't belong in source control, I say an entire project should be stored in source control. That way if my development system goes down I can switch to another and after a couple minutes of downloading the project I'm back to coding.

like image 102
Spencer Ruport Avatar answered Jan 01 '23 17:01

Spencer Ruport