I am wondering if people have a recommendation or a best practice for
the best way to test an update site prior to publishing the content to
the actual live pubic server. I can easily test making a new install by
simply pointing to a local update site, but I haven't been able to
figure out how to test detection and application of an update to an
existing installation. The features in the existing installation have an
update site reference to our public update site, so they will go looking
updates there. I guess what we need is a way to tell the update manager
/ p2 that when it sees a certain update site url, it should use a
different one instead. Does something like this exist? Is there another
approach that people would recommend for this situation?