Where the release files live

Two folders, both shown on the Releases screen, and both changeable there.

• Drop folder — where you put ZIPs for the hub to pick up.
• Package folder — where the published ZIPs are kept, and what customer sites actually download through their signed link.

By default both sit under uploads/keen2support/releases/ and are kept off the web by an .htaccess file the hub writes itself. That works, but it is a mitigation rather than a property: a change of document root, or a server that stops honouring .htaccess, would turn the package folder into a public download of every paid build.

Pointing both above the web root removes that risk entirely — nothing outside the web root can be served however the site is configured. Give the full path from the root of the server; the folder has to exist already and be writable.

Changing the package folder moves the published ZIPs with it. Only the file name is stored against a release, so moving the files is the whole job — nothing in the database needs changing. If any file will not move, nothing is changed at all, because half a store in each folder would mean different sites getting different answers.

There is no falling back to the default if a folder later goes missing. Sites are told there is no update, and the Releases screen shows the fault — better than quietly serving nothing from an empty old folder for a week.