From 7b050e1ada5338242f26d8e55789c0a6f949536b Mon Sep 17 00:00:00 2001
From: Clinton Ebadi <clinton@unknownlamer.org>
Date: Fri, 25 Apr 2014 18:02:12 -0400
Subject: [PATCH] boostrap: fail on error, create cert for local machine

---
 bootstrap/README    | 10 ++++++++--
 bootstrap/bootstrap |  6 +++++-
 2 files changed, 13 insertions(+), 3 deletions(-)

diff --git a/bootstrap/README b/bootstrap/README
index a5115fc..658f047 100644
--- a/bootstrap/README
+++ b/bootstrap/README
@@ -10,7 +10,13 @@ Basic bootstrapping
    - You unfortunately have to duplicate the value of Config.caPath here
  - Run domtool-create-ca to boostrap your local domtool ca
  - Run domtool-init-truststore to initialize the trust store
- - Run domtool-init-acl $user to add yourself as an administrator of domtool
- - Create needed work directories
+ - Run domtool-init-acl $you to add yourself as an administrator of domtool
+ - Run `domtool-addcert $host -unsafe` where $host is the short name
+   of the machine that will run domtool-server. E.g. for
+   "foo.test.domain", $host = foo. Repeat for any machines that will
+   be domtool workers.
+ - Start domtool-server
+ - Run `domtool-adduser $you -unsafe' to create your certificates and
+   grant yourself access to your $HOME path
  - In theory, domtool should start and you should be able to grant
    yourself domains and configure things
\ No newline at end of file
diff --git a/bootstrap/bootstrap b/bootstrap/bootstrap
index ba59893..d109b83 100755
--- a/bootstrap/bootstrap
+++ b/bootstrap/bootstrap
@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/bin/sh -e
 
 # Bootstrap everything for a DEVELOPMENT ENVIRONMENT (an insecure one
 # at that), assuming you are going to be domtool root
@@ -12,3 +12,7 @@ fi
 ./domtool-create-ca -force
 ./domtool-init-truststore
 ./domtool-init-acl `whoami`
+domtool-addcert `uname -n` -unsafe
+
+# Start domtool-server and run:
+#domtool-adduser `whoami` -unsafe
-- 
2.20.1