From 92b78882ab3d333d1e030e4d6b175570a9a0b80b Mon Sep 17 00:00:00 2001 From: Micah Anderson Date: Tue, 27 Jan 2015 14:50:43 -0500 Subject: add information about how the monitor service must be on the webapp node (see #6668) --- docs/platform/guide/nodes.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/platform/guide/nodes.md b/docs/platform/guide/nodes.md index bc48ff3..1cfb156 100644 --- a/docs/platform/guide/nodes.md +++ b/docs/platform/guide/nodes.md @@ -20,7 +20,7 @@ Brief overview of the services: * **soledad**: Handles the data syncing with clients. Typically combined with `couchdb` service, since it communicates heavily with couchdb. * **mx**: Incoming and outgoing MX servers. Communicates with the public internet, clients, and `couchdb` nodes. * **openvpn**: OpenVPN gateway for clients. You need at least one, but want as many as needed to support the bandwidth your users are doing. The `openvpn` nodes are autonomous and don't need to communicate with any other nodes. Often combined with `tor` service. -* **monitor**: Internal service to monitor all the other nodes. Currently, you can have zero or one `monitor` nodes. +* **monitor**: Internal service to monitor all the other nodes. Currently, you can have zero or one `monitor` service defined. It is required that the monitor be on the webapp node. It was not designed to be run as a separate node service. * **tor**: Sets up a tor exit node, unconnected to any other service. * **dns**: Not yet implemented. @@ -55,41 +55,49 @@ What nodes do you need for a provider that offers particular services? Node Type VPN Service Email Service +Notes webapp required required + couchdb required required + soledad not used required + mx not used required + openvpn required not used + monitor optional optional +This service must be on the webapp node tor optional optional + -- cgit v1.2.3