New more appropriate names and structure?
I think since the program has evolved far beyond just monitoring it would make sense to name it to something more all-encompassing.
- overal program suite name ideas:
- HydraHive or HivemindHydra (since it's used with DragonHive) and has multiple 'heads'/subroutines
- the Scheduler could stay as 'ScheduLizard' since that name is still appropriate and good
- BorgLizard could have a bit more original name although it is indicative of its purpose
- Should probably be part of some 'BackupBold' or alike that delegates backups to underlying other parts such as BorgLizard, but also hypothetical RsyncLizard/etc
- JournalMonitor is decent but could be more original?
- notification_tooter should have a more appropriate scaly name
- CachetHelper and StatusHelper and LogHelper and DockerHelper and VariableStorageHelper should probably have more scaly names? or are Helpers exempt?
- Also should Helpers all be together in one directory, or have sub(sub) directories for each Helper backend? Since if we have a dockerhelper, we'll also have a podmanhelper, kubehelper, lxchelper, and since we have a cachethelper relating to statushelper we'll also have a statuspagehelper, and potentially a custom nodejs based statuspage helper (https://git.dragonhive.net/dragonhive/statuskobold) etc.
- docker_updatechecker and such will probably get pulled apart into MoltingManager and a small lizard that will just pull docker updates, a lizard that pulls git updates, a lizard that pulls other types of updates, a lizard that runs any container-specific post-update upgrade/migration scripts, etc.
- I think it would make sense to come up with some scheme that determines the appropriate extension (e.g -lizard or -kobold or -dragon?) is for a specific script, based on the size and its 'independence' from other scripts. E.g a dragon should be able to self-manage entirely and run even if nothing else runs, a kobold might depend on a dragon, a lizard might be interdependent on other lizards and/or kobolds/dragons, or perhaps run a very small thing that will never fail but may also not do anything useful if the kobols/dragons aren't up (for example a tooterlizard for mastodon updates pulled from the notificationbuffer)