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.
¡¡¡¡ Warning, if not done correctly, the database could be exposed !!!!
expose mongo database, but use the firewall to block all IP address except the ones you like.
Useful for load balancing without the use of a database service. Also for use an external database inspection tool.
Example use:
module.exports = {
servers: {
one: {
// TODO: set host address, username, and authentication method
host: '1.2.3.4',
username: 'root',
// pem: './path/to/pem'
// password: 'server-password'
// or neither for authenticate from ssh-agent
}
},
meteor: {
// TODO: change app name and path
name: 'app',
path: '../app',
},
mongo: {
port: 27017,
version: '3.4.1',
servers: {
one: {}
},
ipwhitelist:[
'0.0.0.0' //example ip
]
}
};
The only thing that changes from the original is the "ipwhitelist" parameter, it accepts multiple IPs. And if not present, the mongo docker uses the default configuration and mup won't try to expose it.