windows- and linux-installer (linux does not install softwarebasics
like apache, mysql and php, windows does)
updater is only for linux
updatewizard and process, which does: automatically check for updates and automatically and seemlessly updates the system if no ini-adjustments and new software-components are necessary and otherwhise sends email to admin; presents ini-adjustments to admin in webwizard
if translate5 is updated, while user has active session, for each REST-call an exception is thrown which tells the user to refresh the frontend (and does automatically do so, if the user clicks yes) and it is ensured, that all JS- and CSS-sources are really refreshed by using of versioning-id-parameter
one possible way: prepend to all URLs a /V123/ string, so that JS and CSS are updated in the browser cache, and the server side can recognize if the client is outdated.
systemuser that triggers the autoupdate must have write-access for the whole application and access to mysql via php. Enable the update-kit to be able to run under a different vhost than translate5 via suphp in order to not expose write access for all install-files to normal webserver.
Database Handling:
respect partioning
since updater needs SQL alter Fragments we need a maintaining mechanism (track already installed SQL files)
provide a way to maintain client specific changes (like BEO)
for installing a complete SQL Structure is more useful, so creating a fresh, full SQL structure should be done automatically on building releases. Perhaps only for majors, and minors are always doing alters or so.
Sub-task