oxidized.git - configuration backup software

Age	Commit message (Collapse)	Author
2016-02-25	Changed configuration item names	awlx

2016-02-25	Removed unnecessary repetition	awlx

2016-02-25	Added support for SSH Key usage and ssh-agent-forwarding	awlx

2016-02-19	refactor `#remote_repo` to not rely on `#single_repo?` config	Danilo Sousa
	even in the case we have groups, we can assume is only one repository if the `remote_repo` config is a String.
2016-02-19	move the groups remote to the hook config	Danilo Sousa
	thanks to @ElvinEfendi for the idea! :+1:
2016-02-19	fix 'GithubRepo#single_repo?' private method	Danilo Sousa

2016-02-18	create tests for `GithubRepo#validate_cfg!` method	Danilo Sousa

2016-02-18	fix `githubrepo` hook for groups repositories remotes	Danilo Sousa
	when there was a repository per group we could not use the hook for pushing since we only had one remote configured. This PR configures each repository its own remote based in the `groups` config, as follows: ``` --- groups: first: remote_repo: git@gitlab.lab:oxidized/first.git second: remote_repo: git@gitlab.lab:oxidized/second.git ```
2016-01-04	Merge remote-tracking branch 'upstream/master' into merge-upstream	Elvin Efendi

2015-12-27	expose git repo name and commit oid in hook mechanism and environment variables	Nick Hilliard

2015-12-13	do not commit when there is no diff	Elvin Efendi

2015-12-13	let user configure which auth method to use	Elvin Efendi

2015-12-08	warn when there is a conflict	Elvin Efendi

2015-12-07	pull origin/master before pushing	Elvin Efendi

2015-12-04	consider local repo main	Elvin Efendi

2015-12-04	user password username for github api	Elvin Efendi

2015-11-13	githubrepo hook spec	Elvin Efendi

2015-11-13	do not rescue general exception	Elvin Efendi

2015-11-13	raise more specific exception when required key is not present	Elvin Efendi

2015-11-13	a callback to push config changes to a remote repository	Elvin Efendi

2015-09-17	restore ruby 1.9.3 compatibility0.8.1	Saku Ytti
	fix some whitespaces bump up gemspec version
2015-08-28	Initial implementation of the hook feature	Anton Aksola
	The current implementation is modular and allows users to define hooks in several ways: * Use one of the built-in hook types (currently only 'exec') * Define their own Hook classes inside ~/.config/oxidized/hook Exec hook type runs a user defined command with or without shell. It populates a bunch of environment variables with metadata. The command can either be run as synchronous or asynchronous. The default is synchronous.