*** DEPLOYING AN APPCODEPACK PACKAGE ON SERVER CANNOT BE UNDONE *** ** TO UPGRADE/ROLLBACK ANY APP ON THE SERVER REQUIRES TO UPLOAD A NEW APPCODEPACK PACKAGE ... **
    * APPCODEPACK PACKAGE DEPLOYMENT INSTRUCTIONS: *
    	1. SELECT an AppID from the list below and UPLOAD a valid AppCodePack Package (.z-netarch, NetArchive format, created by AppRelease.CodePack) that match the selected AppID using a valid AppID-Hash.
    	2. AFTER THE UPLOAD, if the Package is validated, IT WILL BE DEPLOYED on the Apache/PHP server within the coresponding AppID folder (directory).
    	3. Deploying the Package on the server WILL REPLACE ANY EXISTING FILES AND FOLDERS within the coresponding AppID base folder, if they exist in archive, except: [ `tmp` folder, and @symlinks ].
    	4. If the Package archive contains a file or folder named `tmp` or a file or folder that match an existing @symlink it will raise a fatal error !
    	5. If the Package contains a file `maintenance.html` in the root of the archive the HTTP 503 Maintenance Mode will be automatically enabled (must be supported also by http server or .htaccess settings).
    	6. If the Package contains a file `appcode-upgrade.php` (App Deploy Task/Upgrade script) it will be executed prior to disable the Maintenance Mode.
    	7. If there are any errors while running the `appcode-upgrade.php` script there are 2 options: deploy a new package or fix the problem manually by removing the maintenance and upgrade files ...

Max File Size support (php.ini): [###MAX-UPLD-SIZE|html###]
[%%%IF:HTML-WATCH:!=;%%%]
[###HTML-WATCH###]
[%%%ELSE:HTML-WATCH%%%] [%%%/IF:HTML-WATCH%%%]