Apply lessons learned after running the first House application in a …

…container

Dockerfile

@@ -0,0 +1,4 @@
+FROM debian:stable-slim
+COPY . /
+RUN apt-get update && apt-get --yes install ca-certificates openssl
+ENTRYPOINT [ "/usr/local/bin/waterwise" ]

Makefile

@@ -47,3 +47,17 @@ uninstall:
 purge: uninstall
 	rm -rf /etc/default/waterwise
 
+docker: all
+	rm -rf build
+	mkdir -p build
+	cp Dockerfile build
+	mkdir -p build/usr/local/bin
+	cp waterwise build/usr/local/bin
+	chmod 755 build/usr/local/bin/waterwise
+	mkdir -p build/usr/local/share/house/public/waterwise
+	cp public/* build/usr/local/share/house/public/waterwise
+	chmod 644 build/usr/local/share/house/public/waterwise/*
+	cp /usr/local/share/house/public/house.css build/usr/local/share/house/public
+	chmod 644 build/usr/local/share/house/public/house.css
+	cd build ; docker build -t waterwise .
+	rm -rf build

README.md

@@ -31,3 +31,7 @@ The timestamp field represents the time of the request, the host field represent
 The origin field represent the URL used to obtain the index. The state field is either 'u' (not yet initialized), 'f' (failed to access the bewaterwise.com web site), 'e' (malformed JSON data received) or 'a' (active). Except when active, an error field provides a description of the error.
 
 The index field is a percentage (which can be above 100), the received field indicate when this index was obtained, and the calculated field indicates when the bewaterwise.com site calculated the index. (This service use the weekly index.)
+
+## Docker
+
+The project supports a Docker container build, which was tested on an ARM board running Debian. To make it work, all the house containers should be run in host network mode (`--network` host option). This is because of the way [houseportal](https://github.com/pascal-fb-martin/houseportal) manages access to each service: using dynamically assigned ports does not mesh well with Docker's port mapping.