Auto-updating CKAN, progress report

[AlexanderDzhoganov]

I've been working extensively on the auto-update feature the last few days. Here is a checklist of necessary changes and additions in order to make this happen:

• Core
  • [x] Query GitHub for the latest CKAN version and download URL
  • [x] Query GitHub for the release notes
  • [x] Query GitHub for the download URL of the latest updater app build
• Command-line client:
  • [ ] A new command to display the latest CKAN version
  • [x] A new command to update to the latest CKAN version
• GUI client:
  • [x] Form to host the new auto-update options
  • [x] Dialog that warns user of a new CKAN version
  • [x] Dialog that prompts user to automatically check for updates (first run only)
  • [x] Actual code to do the auto-update
• Other:
  • [x] CKAN-autoupdate repo to host the updater application, CI integration

[hakan42]

Nice :+1:

[alampros]

Very nice indeed! :+1:

Is it too soon to start thinking about fetching the release notes in these commands along with the version info? This would let you do something similar to the standard autoupdate frameworks out there (Sparkle or NetSparkle).

NetSparkle's UI:

[birdspider]

Just a reminder that for instance on linux where ckan is installed via package managers, auto-update might fail due to permissions or/and might not be desired.

So a option for not using it would be nice. (compile flag, setting, cli option, ...)

This mostly affects the point 'Actual code to do the auto-update'

[AlexanderDzhoganov]

@alampros Suggestion noted, thanks.

@birdspider Auto-update will be 100% optional and off by default.

[AlexanderDzhoganov]

After a series of PRs which I can't be bothered to list, the auto-update functionality is pretty much complete. v1.6.3 contains all the auto-update stuff :tada:

Tested on Windows and Ubuntu 14.10.

[hakan42]

:+1:

[Ippo343]

@AlexanderDzhoganov , you ROCK!

[alampros]

Great work! Thanks @AlexanderDzhoganov ! :neckbeard: