Solved Automatically update plugins?

Hey,

It's very tedious when you have multiple plugins, updating them manually.

Get about 20 emails a day saying there's an update, update it or the server wont work.

Can this be automated ? Make an oxide UI with a plugin update feature ?


Thanks,
Danny

 

I'm not sure it is, otherwise they would've done something already. Though it's always a good idea.

My past scripting experience came from Eventscripts for Counter-Strike: Source, which is basically Oxide for CS:S, but only that it only supports Python.
They had this feature which was few console commands to install or update plugins remotly from your server, there was the command es_install *plugin name or id* (obviously to install the plugin), es_update *plugin* (to update the plugin in case it has been installed with es_install and if the version doesn't not match the ES website), and there was also a command to remove the plugins if im correct. Though you could only use these commands on plugins that were approved by the devs of Eventscripts, which basically the plugins had some sort of compatibility with the installation process. And mine actually supported that. (SAM addon page or official forum post)

I wonder if some time we are going to use a system of this kind.

 

yeah that would be great

 

thanks for confirming!

 

Automated updating.

Why? It is the one thing holding oxide down: updates. It requires to much time and admin-work, and it comes back every week or more often.

The situation is painfull for every server-admin: 'an update is due, have to watch the version number' 'update is out! Have to shut the server down untill oxide is in order (or wipe it again after oxide comes online=angry players)' 'Is oxide out already? Extract it over the latest version of Rust!' 'are the plugins loading? If not: wait? Disable them? Panix!' 'ah, everything is working, lets go to sleep' (quickfix coming trough!).

Most of this hassle can be automated.
-periodically compare the current version of Rust running, and the latest update version rolled out
-when different: either take each server down or toggle switch on the (not yet made) 'autokicker due to update'-plugin, that basically kicks everybody with a message that is on, or wants to get in.
-periodically poll the latest version (on oxidemod.org) of Rust that Oxide supports: if that is the same, download it, stop server, extract it, start server
-somewhere in the oxide-cfg, have a list of extensions with 'latest Rust version supported' datetime
-periodically poll the latest version (on oxidemod.org) of Rust that that Oxide-extension supports: if that is the same, download it, stop servers, copy it, start servers (which is a pain to do I think, but must be possible)
-somewhere in oxide-cfg, have a boolean 'developer' flag indicating if user is oxide-server-admin or oxide-server-developer (aka Wulf and co).
-for each server-identity, have some config file that holds a list of plugins with name, latest rust version supported, an 'essential' boolean flag

When not developer:
-periodically poll the latest version (on oxidemod.org) of Rust that that Oxide-plugin supports: if that is the same, download it, copy it
-when all 'essential' plugins are 'in', switch the autokicker-plugin off
-stop periodically checking when all plugins are accounted for

When developer (developer needs to have a small server up and running at all times)
-developer has all maintained plugins in his config file
-pulls the latest version of all plugins, even when current 'lateste version' of Rust is different
-copy them one by one, catching if they loaded fine, when they do: update their 'latest version' file on oxidemod.org, when they dont: send maintainer an email with the actual error

Also:
-Give maintainers (and/or oxide-developers) a way to update plugin + version information that is available on oxidemod.org
-developer of oxide should also get email (or whatever) when there is an update detected.
-add some config options like 'check version every x seconds' and 'WhatToDoWhenUpdating=Run Vanilla OR Take Server Down OR Use AutoKicker' and such.

So, there it is: the outline of a 'as smooth as we can get it' experience for the server-admins: They wont even have to stay around when the update rolls out. Yes, it is a pretty amount of work, but 'update hell' is wearing servers-admins out, imho. Update hell=over=many more server-admins will start to use oxide plugins.

 

If it all was simple...

 

Well there is à plugin that Will test most of the time what plugin has à new version

 

When plugins no longer work after an update, is there a way to have them get automatically updated? Or do we have to re download them and replace them?
Thanks-

 

AFAIK you have to download and replace them.. i heard something about "Multiplay" is like a server provider for Rust ? I'm not familliar with it.. but someone said to me that they are updating the plugin or sth like that.. i dont really wanna tell you shit

 

Here is a little Powershell script that you can use to update your oxide plugins. As said in my post I'll make something more advanced taking into account the whole update procedure. (Server update, Oxide update, *.IO update, Plugin update, Server Start/Stop/Restart and of course user notification)

[Script] Rust – Oxide plugin Downloader | Powershell in Avalon

 

This is no longer working