1.2.0: Location and name defaults update #227
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…day debs) use as default location. This will avoid permissions issues on the docker image too
dbmurphy
approved these changes
Sep 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Now that we build Docker containers and Release binaries/RPMs using a default backup location and name will simplify using the tool.
Default location (used by RPMs/Docker): /var/lib/mongodb-consistent-backup
Default backup 'name': "default"
This will greatly simplify the use of the Docker container. Currently people need to guess or know where the data dir with the right MCB-user ownership is. This also makes the tool behave the same as mongo, mongorestore, mongodump, etc, ie: use defaults if no flags provided.
This completes the 1.2.0 release and I propose a code freeze of it.