Support deploying a server from scratch #8
Description
The update process for RustDedicated, Oxide, and even Oxide plugins also covers most of the same steps needed to perform an initial install, so it might be convenient to support having RLS do this in order to reduce admin workload even more.
This isn't entirely trivial, however - here are some concerns off the top of my head:
- RLS currently gets the SteamCMD path from post-install files; would need to have the user either specify the path to SteamCMD, or put it in the OS search path
- Probably need to support populating player ID lists (owner/admins/bans?) via RLS config file, or deploying pre-created versions of these files before initial launch?
- May need to support deploying pre-created Oxide config files?
- May need to support a list of one-time RCON commands (mainly for configuring Oxide, but could also be used to implement the ID list stuff above)