Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have one (for now) large text data file of 120 MB.
Is it a poor practice to put it in the repo? Does it affect search functionality on GitHub?
It seems like it is a bad idea because the entire source code is only 900 lines.
Not planning on updating the file.
Could put it on Dropbox or Google Docs, but then it is separate from the repo.
If not GitHub, is there a better way of managing/backing up large data files?
Put it in the repo if:
1- you want to keep track of the changes
2- it is actually a part of the project and you want people to receive it when they clone the repo
Don’t put it in the repo (use .gitignore to exclude it) if:
1- it changes often but the changes are not meaningful and you don’t want to keep the history
2- it is available online or you can make it available online and put a link or something in the repo for people to know where to find it
Dropbox is good if you don’t have lots of people downloading it, Amazon S3 is your best bet for hosting it.