[DOCS-3054] Comment on: "manual/tutorial/install-mongodb-on-os-x.txt" Created: 02/Apr/14  Updated: 11/Jan/17  Resolved: 17/Apr/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Minor - P4
Reporter: Docs Collector User (Inactive) Assignee: Randall Hunt
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

osx mavericks

Location: http://docs.mongodb.org/manual/tutorial/install-mongodb-on-os-x/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.152 Safari/537.36
Referrer: http://docs.mongodb.org/manual/tutorial/install-mongodb-on-os-x/
Screen Resolution: 1440 x 900
repo: docs
source: tutorial/install-mongodb-on-os-x


Participants:
Days since reply: 9 years, 44 weeks ago

 Description   

In version 2.4.2 or somewhere around there, when installed with homebrew you could just type: mongod and it would default to the /usr/local/var to store the databases. Now you have to pass the `--config /usr/local/etc/mongod.conf` flag for it to load the dbs from there. Is there anyway to change this back.

Right now I have an alias set up to so I don't have to type `mongod --config /usr/local/etc/mongod.conf`



 Comments   
Comment by Randall Hunt [ 16/Apr/14 ]

Currently I think the best solution is what is outlined in

brew info mongodb

caveats section:

==> Caveats
ln -sfv /usr/local/opt/mongodb/homebrew.mxcl.mongodb.plist ~/Library/LaunchAgents
 
To reload mongodb after an upgrade:
    launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.mongodb.plist
    launchctl load ~/Library/LaunchAgents/homebrew.mxcl.mongodb.plist

If that resolves this issue I would like to close it.

Then you can start/stop mongodb with

$ launchctl start mongodb
$ launchctl stop mongodb

Comment by Randall Hunt [ 03/Apr/14 ]

I proposed another change that would have kept the behavior the same without modifying the 'bin' directory but the homebrew crew decided to go with another patch.

I explained my reasons for it in the pull request but I'll reiterate them here.

Modifying the default behavior of mongod damages the ability of lots of scripts to function. In Homebrew's case they were taking the existing mongod binary out of the bin folder where it expected to be and replacing it with a ruby script that called mongod with certain arguments. The problem was that the script would ALWAYS load the config which would silently introduce additional arguments that the scripts running servers had no means to divine.

I proposed creating a separate "mongodb" command that had the original behavior and could coexist in the bin directory. This was rejected and they removed the script entirely instead. I still believe this is more desirable than launching with silent defaults.

2.6's config file and config file parsing may make it possible to do something better with this.

Comment by Tyler Brock [ 03/Apr/14 ]

Randall you made this change to homebrew right?

Generated at Thu Feb 08 07:44:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.