I’m currently coding up the server-side of a webapp for the first time in my life. I’m using nodeJS, and plan on using MongoDB as my database with that. On the MongoDB website, their tutorial goes through downloading and extracting the mongoDB files into a local folder, but I’ve already installed everything via aptitude.
Is there any advantage to keeping the database files in a local folder that way instead of using a package manager? I feel like updating the code in the future when there are new MongoDB releases will be easier via a package manager, but I really don’t know for sure.
Would somebody be able to lay out some of the advantages or disadvantages of using one method vs the other? If I was planning on using mongoose with this in the future, would using one method vs the other make a difference?
Best, and Thanks,
Sami
Package manager pros:
Package manager cons:
The problem here is that 10gen has been really sketchy with their package names. Currently the package name is
mongodb-10gen, a few months back it wasmongodb-stable. Version 1.6 to 1.8 had breaking changes, the same may be true of 1.8 to 2.0 (or 1.10 or whatever…).You’ll note there’s no version number in the package. So one day you could add a server and find it running 1.10 instead of 1.8. (which may break code)
With MongoDB being the young product that it is, it’s best to just keep a copy of your “current dev” build so that you can deploy the correct version to all servers. The whole
wget / tarprocess isn’t really that hefty.