Merge pull request letsencrypt#554 from letsencrypt/remove-monolith

jsha · jsha · commit 30624a332dc3 · 2015-08-05T11:45:44.000-07:00
Remove monolith
diff --git a/DESIGN.md b/DESIGN.md
@@ -1,8 +1,7 @@
 # Boulder flow diagrams
 
 Boulder is built in a rather decentralized way in order to enable different
-parts to be deployed in different security contexts.  (Of course, they can
-also be run together, as in `./cmd/boulder`.)
+parts to be deployed in different security contexts.
 
 In order to you understand how boulder works and ensure it's working correctly,
 this document lays out how various operations flow through boulder.  We show a
@@ -18,9 +17,7 @@ A couple of notes:
   (certificates), and read by WFE, RA, and CA.
 
 * The interactions shown in the diagrams are the calls that go between
-  components.  These calls can be done directly (as in `./cmd/boulder`), or
-  they can be done via the AMQP-based RPC code in `./rpc/`.  We do not
-  distinguish between those cases here.
+  components.  These calls are done via the AMQP-based RPC code in `./rpc/`.
 
 
 ## New Registration
diff --git a/Dockerfile b/Dockerfile
@@ -48,7 +48,6 @@ COPY . /go/src/github.com/letsencrypt/boulder
 # Build Boulder
 RUN go install \
   github.com/letsencrypt/boulder/cmd/activity-monitor \
-  github.com/letsencrypt/boulder/cmd/boulder \
   github.com/letsencrypt/boulder/cmd/boulder-ca \
   github.com/letsencrypt/boulder/cmd/boulder-ra \
   github.com/letsencrypt/boulder/cmd/boulder-sa \
diff --git a/Makefile b/Makefile
@@ -11,7 +11,6 @@ MAINTAINER ?= "Community"
 
 OBJECTS = activity-monitor \
 	admin-revoker \
-	boulder \
 	boulder-ca \
 	boulder-ra \
 	boulder-sa \
diff --git a/README.md b/README.md
@@ -30,13 +30,21 @@ A quick-start method for running a Boulder instance is to use one of the example
 > docker run --name=boulder --read-only=true --rm=true -v $(pwd)/.boulder-config:/boulder:ro -p 4000:4000 quay.io/letsencrypt/boulder:latest boulder
 ```
 
+Alternatively, to run all services locally, using AMQP to pass messages between them, you can use:
+
+```
+> python start.py
+# start.py will use the configuration specified by BOULDER_CONFIG or test/boulder-config.json
+```
+
 To run a single module, specifying the AMQP server, you might use something more like:
 
 ```
 > docker run --name=boulder --read-only=true --rm=true -v $(pwd)/.boulder-config:/boulder:ro quay.io/letsencrypt/boulder:stable boulder-ra
 ```
 
 
+
 Quickstart
 ----------
 
diff --git a/cmd/boulder/main.go b/cmd/boulder/main.go
