From 6709929b5748168c0b29cebb231a8b8f81428fa9 Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Tue, 9 Dec 2014 11:10:27 -0800 Subject: document SSH key setup requirements --- README.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index 35d1de4..8768320 100644 --- a/README.md +++ b/README.md @@ -52,6 +52,8 @@ Savage accepts exactly one optional command-line argument, which is the port num When running Savage, its working directory needs to be a non-bare git repo which is a clone of the repo being monitored. +The Unix user that Savage runs as needs to have an SSH key setup, and that SSH key needs to be registered in Savage's GitHub user account, so that Savage can pull-to/push-from GitHub securely via SSH. + If you're using Sauce, we recommend [using a sub-account](https://saucelabs.com/sub-accounts) for Savage, to completely prevent any possibility of compromise of your main account. Other settings live in `application.conf`. In addition to the normal Akka and Spray settings, Savage offers the following settings: -- cgit v1.2.3