While automation is nice, a malicious actor could use this updater to execute arbitrary code on the target machine. You can also host your own custom recipes as you like for any SRCDS+SourceMod server setup. This resource is still work-in-progress, more curated lists to be added later! If you are operating a Neotokyo SRCDS, this project offers some recommended recipe(s) here. You should always use the default self-updater recipe to keep the soup script itself updated. For example, you can have some trusted recipes auto-update their target plugins without any admin intervention, but choose to manually update more fragile or experimental plugins as required (or not at all). The purpose of soup is to reduce SRCDS sysop workload by making SourceMod plugin updates more automated, while also providing some granularity in terms of which plugins get updated when, with the introduction of maintained/curated recipes. For a SourceMod plugin, this means any new updates get automatically applied upon the next mapchange after the completion of a soup update cycle. This will automatically keep such resources in-sync with their remote repository. It parses soup recipes, remote lists of resources to be kept up-to-date, compares those resources' contents to the target machine's local files, and re-downloads & re-compiles them if they differ. Soup is a Python 3 script, a SRCDS SourceMod plugin update helper, intended to be invoked periodically by an external cronjob-like automation system. This project started as a custom utility for the Creamy Neotokyo servers (hence the name), but open sourcing and generalising it for any kind of SRCDS/SourceMod servers seemed like a good idea, in case it's helpful for someone else too. CreamySoup/"Creamy SourceMod Updater" (or just soup for short), a helper script for automated SourceMod plugin updates management.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |