Add .rsyncignore.local to .gitignore #144
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: This PR is primarily aimed at the TBP team.
What
This PR adds
rsyncignore.local
to.gitignore
.Why
Excluding certain files and folder from
rsync
's purview shaves off precious seconds when creating EC2 instances. When we run experiments on AWS, an EC2 instance is created for each experiment, which is then updated with local copies oftbp.monty
andmonty_lab
viarsync
. Much ofrsync
's time is spent uploading files that might not be necessary for your particular purposes, such as syncingdocs
when running an experiment. It would be preferable to prevent user-specificrsync
settings from being tracked.How
A couple of lines were added to
.gitignore
.This PR is to accompanied a corresponding change in internal tooling to recognize
rsyncignore.local
files intbp.monty
.