What is the "correct" alternative to MongoDB on Fedora? Maybe I can build a different database binding...

By the way, I just added auto-backup into MeshCentral 0.3.4-t, add this to the "settings" section:

"AutoBackup": {
  "backupInvervalHours": 24,
  "keepLastDaysBackup": 15,
  "zippassword": "test"
}

This will zip a new backup every 24 hours and place the result in "meshcentral-backup". You can optionally say how many days before removing old backups and if you want to password protect the backup zip file, you can set a password. If you use MongoDB, it will call "mongodump" to backup the database and include it in the .zip file.

@scotth Note that MeshCommander is built into MeshCentral. Once you get MeshCentral running, click on a device and if it has Intel AMT, you will see a "Intel AMT" tab. The content of that tab is MeshCommander.

If you just want a Intel AMT console and connect to AMT devices on the local network or using a VPN, use MeshCommander. If you want a more completely management solution with AMT support included use MeshCentral.

Hope it helps.

@scottalanmiller Now that I have more experience with NeDB, it's possible MongoDB is mostly overkill. The only need for MongoDB is for server peering in the future. I will have each MeshCentral server listen to the change events from the database and use that to synchronize state. I started work on this, but it's still a ways out.

@Ylian Actually... section 8.4 of the MeshCentral User's Guide does explain how to do the conversion.

@scottalanmiller Agreed, I use...

node node_modules/meshcentral --dbexport bob.json

then setup MongoDB in the "meshcentral-data/config.json" and do

node node_modules/meshcentral --dbimport bob.json

However, I need to write this up more formally. This technique will also not migrate general events and power events, so I got some improvements to make.

@scottalanmiller Your right, the built-in DB (called NeDB) is really fast and will probably handle a 1000 devices without any issues and with much less RAM than MongoDB. I run MeshCentral on Raspberry Pi and AWS t3.nano instances and you really don't need MongoDB.

On another note, seems like I will need to take a look at MeshCentral installation on the latest Ubuntu versions

@smartkid808 As long as you have a backup of "meshcentral-data" and "meshcentral-files" you should be fine. You can wipe the "node_modules" folder and just do "npm install meshcentral" again to get it back and you in business again. Or wipe everything, install from fresh and put the "data" and "files" folders back. There is nothing magical in "node-modules" so you can keep a copy of it just in case or wipe it and re-install anytime.

Note that your should run "npm install meshcentral" in the "/home/wscheele" folder in your case. Don't go in the "node_modules" folder that run "npm install", always run that command outside the "node_modules" folder.

@smartkid808 If you see this error:

Error: ENOENT: no such file or directory, open '/home/wscheele/views/layouts/main.handlebars'

This was due to a new version of express-handlebars 3.1.0 that broke MeshCentral. I released a new version of MeshCentral last night v0.3.4-k with a fix for this.

This is an interesting suggestion! Can someone send a screen shot of that this landing page look like on other products?

FYI. Started work on a night-mode user interface for MeshCentral. It's in v0.3.4-b, but need to do a bunch more work to get it nice.

@MordyT One more thing. If you can go in "MeshCentral-Data" and look at the size of the ".db" files... Is any of the files really big (Megabytes)? If so, what is the name of the file that is big and how big is it? With only 10 PC's, I can't expect any of the files in that folder to be of any significant size. - Thanks.