Some feature ideas

[D4VOS]

• detection of updates in the workshop while the server is running + automatic restart e.g. 10 min after detection
• tbh I use your manager mainly because of super easy management of mods, watchdog server and hooks. It would be ideal if there was an option to disable the webserver, api at all e.g. via config. It would save a few server FPS
• multithreaded/async hooks, currently before each server start I backup the most important files and send them to a network drive (using beforeStart hook), it would be ideal if I could separate these actions and the sending files in the e.g. afterServerBoot hook, right, so as not to delay it

[radixtenshi]

Im actually using this hooks feature to clean the logs that start to become a problem qhen you add a mod that write to many script errors.

I have already tried to go on the way to perform backup every time that the Server restarts. But the truth is that it is not practical. Ideally, the times of the backup routine and those of server restart should not be linked. The backup must perform atmens daily (once per day) or what the administator considers necessary. But in cases where the server restarts several times a day for a reason outside the normal routine, it ends up having a backup for each restart and is not useful in terms of information protection or even to reverse the changes. Ideally, the backup is handled through the scheduller of the operating system with a specific script for that task. In my case I do it with the Aomei Backuper tool, but it is not necessary to have a third -party tool.

• For the detection of updates in the workshop while the server is running + automatic restart e.g. 10 min after detection.

Also try to solve it that way. The problem in this case is as follows:

It has happened to me that the developer of some mod was implementing a new version and in this process performs more than one update in a question of hours or minutes. I do this myself, but for such a case I have an exclusive test server. If a mod that you has aggregate begins to have this behavior, control the restart of the server. In addition, this could be used as a denial of service attack. The ideal in this case is that at most notify the changes, but not to send a forced restart.

---

I suggest adding the functionality to perform a backup one, or more than a specific folder and compress this result by handling independent times of the programmed server restart. That would be very useful for those who do not have the ability to generate their own scripts.

I also like the idea of adding the option to completely deactivate the web interface. It is true that for those who do not use it, I will save fps.

On the other hand, I would love that web interface can be added more advanced functionalities, for example similar to the functionalities that Cftools has. Something basic no so complex, but it would be ideal like Battlemetrics.

Anyway, even so, it is still in my opinion the best manager server I have tried.

[mr-guard]

Thanks for the suggestions.

You really dont have to worry about the server FPS impact. The webserver really just idles if you dont use it. You can also check your taskmanager for more details but the server manager is really resource-friendly. The one thing that could actually impact the server fps is the ingame report (not by much, but it could). If you are really concerned about it, there is an option to disable it in the config. If disabled, it wont even load the server manager mods on your server.

[D4VOS]

What exactly is "IngameReport"?

What about mod update detection? It would be very useful feature imo

[mr-guard]

The ingame report is a small mod that send data about the ingame players and vehicles (name, location, health) to the server manager, so you can see it in the web interface

The mod detection is a bit harder to do, as @radixtenshi mentioned. If a modder updates frequently, it might break your server.

It should be off by default, but I might implement that feature in the future

[D4VOS]

The ingame report is a small mod that send data about the ingame players and vehicles (name, location, health) to the server manager, so you can see it in the web interface Thanks for the explanation :D

The mod detection is a bit harder to do, as @radixtenshi mentioned. If a modder updates frequently, it might break your server. It should be off by default, but I might implement that feature in the future

The truth is that we should only use verified and reliable stable mods. Of course, something like this can happen, but it is hard to talk about DDOs here.... We will see that such a thing happens to the server, so we can easily take appropriate action. Such functionality has been in Omega Manager for a long time.

@radixtenshi I would disagree that a reboot backup is not practical. In fact, this is the last moment in which we can make a backup, before an update of some mod can destroy our storage state. Currently, in "beforeStart" I have a script that makes a backup and sends it to an external drive. In addition, I do the same thing in half the time between reboots via Windows Scheduler. With restarts every 6h - I have a backup every 3h. Of course, I also have retention scripts of these backups, but it is not important, these files are not that big.

[radixtenshi]

I think you must first understand how a Backuip scheme works.

You can take all the backups you want, but the important thing is to have a backup that really serves (that is, it is effectively recoverable) and at the same time occupy the minimum of space.

The main objective of a backup is to be able to recover the state of the server in a database failure.

On the other hand, the game has its own backup system that stores the database periodically. This is programmed by the developers themselves and the server stores when developers consider that it is necessary. And if you look, with the backup scheme every 3 hours, the only thing you are doing is to repeat this information 8 times per day since if you observe the folder \ storage_1 \ backup \ (where is the database backed) probably not It has changed a lot.

From what I have seen this automatic system stores modifications of the database throughout the day and even several previous days.

It happened to me to have daily backups and yet just use the files of the carpetya \ storage_1 \ backup \ to recover the base in a case of disaster. You can do the test yourself, to reestablish a backup today, one of 2 days ago and one of 4 days ago and see the changes. I did that test on a test server.

It could be said that the Server already has an included backup system that contemplates the modifications of the database (which is what mods mainly modify or damage).

Considering all this, what would miss supporting? The configurations made by an administrator.

When would it be ideal to support them? Every time the administrator makes a configuration change. Therefore, this part no need to be automatic, with which it is done manually (with a previous Snapshot) that the admistrator plans relevant changes, would be sufficient.

And in conclusion, the Server Manager is not a backup tool, so I would not pretend to manage this aspect when there are tools developed exclusively for this task and of course offer adequate solution.

If your hosting is with an omegamanager interface (which is so obsolete) or a nitrado interface, in that case the ideal is that the backup is handled by hosting itself. If what you have is a VM (Virtual Machine) The ideal is to handle it via Snapshot, it is more efficient and safer.

Of course you can make a script that makes a copy of the files you want, but it's just a copy. It is not technically a backup and also although it serves, it would be the most precarious method.