Rudder

In any given environment, there may exist some nodes which do not have internet access. For initial deployment of the rudder agent, these typically will have their installations done manually by uploading the appropriate package and installing it. For subsequent upgrades however, a typical method for a node with no internet access might be accomplished by using the file download technique with a post-hook which installs the new version of the rudder agent package.

The rudder server typically DOES have internet access, so would it be possible to automatically configure the rudder server to be a repository mirror of the rudder software so that nodes without internet access could simple have their rudder repository definitions point to the rudder server?