...
These are the main URLs that need to be used to access the admin interface, delivery scripts and locally stored images. While these can be edited via the Revive Adserver administrative UI, only one domain can be set for each option.
...
| Code Block |
|---|
;<?php exit; ?> ;*** DO NOT REMOVE THE LINE ABOVE *** realConfig="revive-dev.fornax.net" [webpath] admin="foo.com/www/admin" delivery="foo.com/www/delivery" deliverySSL="foo.com/www/delivery" images="foo.com/www/images" imagesSSL="foo.com/www/images" |
...
| Warning |
|---|
Management of multiple domains is, as mentioned above, not supported by the Revive Adserver administrative UI. If you manually configure the Revive Adserver configuration in this way, it is highly recommended that you set permissions on all additional configuration files so that the Revive Adserver administrative UI cannot edit the files. This will ensure that you don't accidentally update the configuration when accessing the UI via a "secondary" domain; updating the configuration in this way would cause Revive Adserver to create a complete, "primary" domain style configuration, without a |
Single Code Base, Multiple Installations
To be documented.Using the same principles as above, it is possible to use one Revive Adserver code base to run two or more completely independent installations of Revive Adserver.
However, this is generally not recommended, because there are certain operations (e.g. initiating an upgrade) that depend on certain files existing in the Revive Adserver var directory. Thus, it becomes impossible to cleanly manage the upgrade process for each installation separately - all installations have to be taken offline to upgrade each one, and when one upgrade is completed, the upgraded server will be affected when upgrading the next one, etc.
What appears to be a time saving approach in the short term rapidly becomes a complex management issue.
As a result, figuring out how to run multiple installations on one code base is left as an exercise for the reader - if you can figure it out, hopefully, you can see why it's a bad idea. If you decide to use it anyway, and have the skills to code the necessary tools to automate the tasks required so that it's not a bad idea, please consider contributing to the Revive Adserver project!