@spaceshiptrooper wrote:
Yes! Perfect. That never even crossed my mind to allow backups before updates. I'll put this in my todo list.
So speaking about update packages, should I have a list of what has been changed on the automatic update check?
Example: Let's say the update automatically checks for updates. It will display on the admin panel what has been changed in the newer updates. Nothing will be executed until the admin hits a button to update their software. If they decide to hit the submit button, it will
- Make a backup of all files first.
- Then download and extract the files and place them where they belong.
Does this sound like a good idea or should I just make it so that the client has to download the package, extract it themselves, and then allow them to upload it to their server?