I ran mongod with the command mongod -dbpath /data/db/.Įssentially, I’d like to know how the Hombrew and direct download installs differ and how my current setup might mess up future porjects, if at all. Since then, I’ve created a /data/db directory from the root and run both mongod and mongo, including inserting some tests, and everything worked fine. Mkdir data & echo 'mongod -config /usr/local/etc/nf -dbpath=data -rest -httpinterface' > mongod.sh & chmod a+x mongod.sh &. I was really unclear what was happening in step 6, so I didn’t execute that last command: I used this tutorial: How to Install the MEAN Stack on Mac OSX and followed the instructions up until step 5. It is recommended to run MongoDB as a macOS service, as doing so sets the correct system ulimit values automatically (see ulimit settings for more information). Alternatively, you may choose to store the values for dbpath, logpath, fork, and many other parameters in a configuration file. You can run MongoDB as a macOS service using brew, or you can run MongoDB manually as a background process. I’ve already downloaded MongoDB using Homebrew, but a couple of tutorials I watched said that it’s better to download the tarball from the website. To run MongoDB, run the mongod process at the system prompt, providing the two parameters dbpath and logpath from above, and the fork parameter to run mongod in the background. I’m adding MongoDB to my dev environment, and I’m trying to figure out what the fundamental differences between installing with Homebrew and downloading the tarball from the website are.

Mongodb mac os