gitolite/t/keys/config

host *
    stricthostkeychecking no
host gitolite
        identityfile ~/.ssh/tester

host u? gitolite
	user gitolite-test
	hostname localhost
host u1
	identityfile ~/.ssh/u1
host u2
	identityfile ~/.ssh/u2
host u3
	identityfile ~/.ssh/u3
host u4
	identityfile ~/.ssh/u4
host u5
	identityfile ~/.ssh/u5
host u6
	identityfile ~/.ssh/u6
(testing) make t/install not wait to accept host key on first run Please don't use this setting in a production system but in some environments it is needed for completely automated testing to be able to use ssh correctly. 2012-02-11 11:44:22 +01:00			`host *`
			`stricthostkeychecking no`
make gl-system-install easier to run make the arguments optional (with documented defaults) plus they need not exist a priori, reducing one command (the silly mkdir!) that the user has to run. All this is preparatory to deprecating the from-client method. We've even switched the test suite to 'non-root' method now 2011-05-27 06:37:37 +02:00			`host gitolite`
			`identityfile ~/.ssh/tester`

			`host u? gitolite`
finally, open up my secret test scripts... ...after getting rid of most of the hardcoding (though not all!) 2010-06-12 07:33:53 +02:00			`user gitolite-test`
			`hostname localhost`
			`host u1`
			`identityfile ~/.ssh/u1`
			`host u2`
			`identityfile ~/.ssh/u2`
			`host u3`
			`identityfile ~/.ssh/u3`
			`host u4`
			`identityfile ~/.ssh/u4`
			`host u5`
			`identityfile ~/.ssh/u5`
			`host u6`
			`identityfile ~/.ssh/u6`