...
Step 3: Extend the new domain config file to override the "default" domain settings
asdfThe magic that allows this type of setup to be enabled is that Revive Adserver configuration files can contain a realConfig entry, to inform Revive Adserver that the "real" configuration for how it should operate is located in another file, but it is also possible to add regular configuration directives to the same file, which then "override" the configuration directives of the realConfig file.
So, to enable the new foo.com.conf.php file to instruct Revive Adserver that when the service is accessed via the foo.com domain, it should operate using a set of server access paths that are specific to the domain, but otherwise, all other configuration items should be used as configured via the example.com domain configuration file, the foo.com.conf.php file should be extended to be:
| 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" |
Single Code Base, Multiple Installations
...