It is basically a built for the latest MongoDB for Debian.
The current version is the r4.0.5 build (release).
There is a newer version
4.1.0, but given, we use
NoSQLBooster, it only works with
4.0.0 and the
4.0.x is the stable, the next stable will be
4.4.0 and so on...
It will remove all
mongodb* apt packages in
/etc/systemd/system/mongodb-server.service is replaced.
It install the required apt dependencies and generates the
SystemD service and makes it enabled.
Check, if the build works (building is below). It runs all tests, so if it works, then it really does, actually. If there is an error, of course, you will not deploy on your server. So, if building and testing works, then it puts the binaries as it follow and you are sure and done.
For testing, you may build it in Docker, but the live building is on the server in the directory in the GIT repository
build directory and then it puts the files into
It can work with
sudo, but the best if you are
root. Of course, you can check the
code, there is no
harm for sure!
git clone https://github.com/patrikx3/docker-debian-testing-mongodb-stable cd docker-debian-testing-mongodb-stable
If below you get an error, please create an
issue, because it is possible, I have not added a package, because my server was already there, but I will add in it for you for sure with
All defaults are in the config, that MongoDB uses:
It generates everything, all you have to do:
sudo ./scripts/build-server.sh r4.0.5
It generates and install GoLang and builds the tools that you find them in:
Then, it puts all tools into the default Debian
The exact command is like:
sudo ./scripts/build-tools.sh r4.0.5
Before you start the database, but after the build , you are required to create a config (unless, you already have it), a skeleton is here:
sudo cp ./artifacts/root-filesystem/etc/mongodb.conf /etc/mongodb.conf sudo chmod o-rwx /etc/mongodb.conf sudo chown mongodb:mongodb /etc/mongodb.conf
After you created the config, you start the database like:
service mongodb-server start or
service mongodb-server restart