aaron Posted January 19, 2017 Report Share Posted January 19, 2017 (edited) What is the reason Revive Adserver should not be installed from source but instead from a zip on the downloads page (as mentioned in a few other threads)? What will be the consequences if running from source? As of today I use a cloned version of Revive Adserver source in which I have modified some libraries and some delivery files to fit my needs. I would like to use this without suffering the consequences above (depending on the severity). Hence I would like to replicate the Revive Adserver release process to produce a similar zip file as can be found on the downloads page. Any info on this would be very welcome. Edited January 24, 2017 by Erik Geurts Corrected product name spelling Quote Link to comment Share on other sites More sharing options...
Erik Geurts Posted January 24, 2017 Report Share Posted January 24, 2017 The files present on Github are not packaged for installation, the files we publish on the Downloads page are. Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted January 28, 2017 Report Share Posted January 28, 2017 Hi @aaron, Probably the two main differences will be that, when we package up a Revive Adserver release: We strip out some of the files in the repository that are development tools, and are not required for the functioning of Revive Adserver (which may, therefore, introduce a security risk if they are present in your installation); and We "compile" the delivery scripts, merging all of the required source files that are necessary for banner delivery into a single file (per invocation tag type), for performance reasons. Quote Link to comment Share on other sites More sharing options...
aaron Posted March 2, 2017 Author Report Share Posted March 2, 2017 Thanks for the clear response @andrewatfornax and sorry for late response. Would you have a list of files or folders of the development tools that are stripped out ? Merging the delivery scripts I guess you mean running the scripts/delivery/rebuild.php script? Thanks! /Aaron Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted March 21, 2017 Report Share Posted March 21, 2017 Hi @aaron, I think it's: The plugins_repo directory: https://github.com/revive-adserver/revive-adserver/tree/master/plugins_repo The www/delivery_dev directory: https://github.com/revive-adserver/revive-adserver/tree/master/www/delivery_dev And all of the "test" directories throughout the code base Possibly some others - but nothing is jumping out for me right now taking a look through the scripts :-) Yes, scripts/delivery/rebuild.php merges all of the different source files used for each delivery action into a single file per action. This helps give some better performance for users who are not using an opcode cache / haven't configured their cache to ignore checking for file timestamps - otherwise there is a lot of file access required for each delivery action. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.