-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate the data dir into it's own repo #14
Comments
Not a bad idea, but I am not sure how to best do that though. I will ask some Github friends what they suggest. |
I though a little bit about this and I think the best way to go is:
@davidski What do you think? |
Definitely like having |
Cool, will get to it as v0.1.2 :) |
This pull request cleans it up and removes the data, but it will still be in the git history. It seems removing it is a bit traumatic. I will research a bit further on this. |
Thanks, @alexcpsec! FYI, for clearing up the history, I recently used the steps detailed in this Stackoverflow discussion to do a similar bit of git surgery. |
Yeah, I will look into that, Thanks! |
All right! Fixed! This is a good reference for this - https://help.github.com/articles/remove-sensitive-data |
Splitting the data directory out into it's own repo would allow clone operations to run a lot faster. Current repo is 279MB in size. 😬
The text was updated successfully, but these errors were encountered: