On Wed, Feb 1, 2012 at 7:46 PM, Alvaro Lopez Ortega <[email protected]>wrote:
> >>> Better still would be using a git-based versioning system that generates >> a commit with every save, exposing the ability to revert back to a previous >> revision via a simple drop-down listing the sha1 of each of the previous >> commits. There are a ton of additional advantages to moving towards a >> git-based system (ease of deployment of configuration files to other nodes >> via git push, etc.) but this particular capability would be reason enough. >> >> Alvaro, your thoughts? >> > > It's an interesting idea. It'd vote +1 as long as we managed to implement > it as a weak dependency (this is, it'd also work if you did not have git > installed). > You could have some sort of plugin system for Cherokee-Admin, along with a "hook"/callback system that lets plugins hook in to certain events. Then you 'd just need to add a "Configuration saved" hook that a Git / Mercurial plugin could listen to. This would keep the config source control stuff outside of the core.
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
