Viking Configuration Management System
Note
This project is under active development.
Viking CMS is a client/server system. The server runs on one (or more) central machine from which the Viking Agents can request the details of your Longship, which includes your Hammars and Hammar Strikes and multi-tiered rigging (named settings) which each Strike can use.
When an Agent requests its portion of the Longship, it will get back a list of Hammars it needs to download, including their version numbers. This allows Agents to cache Hammar content locally (It shouldn’t change too often, even if your configuration changes), optimising download times.
The Viking Server does not access or run Hammar Strikes, instead all interpretation of the Longship, and Hammar Strikes is done on the Agent. Most machines running VikingServer will, however, also run VikingAgent, to manage their own configuration.
A single run of a Longship is called a Voyage.