summaryrefslogtreecommitdiff
path: root/controller/README.md
diff options
context:
space:
mode:
authorAdam Ierymenko <adam.ierymenko@gmail.com>2016-07-08 13:42:04 -0700
committerAdam Ierymenko <adam.ierymenko@gmail.com>2016-07-08 13:42:04 -0700
commit0e2964261f59f5e614ebcfeffb95d48f0a0a190b (patch)
tree5370288c685b0b9b4cc1f1a34ea8b4bca5d3a46f /controller/README.md
parentffe7d8d024f51624837b22a8285d7432315f4ae8 (diff)
downloadinfinitytier-0e2964261f59f5e614ebcfeffb95d48f0a0a190b.tar.gz
infinitytier-0e2964261f59f5e614ebcfeffb95d48f0a0a190b.zip
docs
Diffstat (limited to 'controller/README.md')
-rw-r--r--controller/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/controller/README.md b/controller/README.md
index 97f073c8..8b789a3e 100644
--- a/controller/README.md
+++ b/controller/README.md
@@ -54,7 +54,7 @@ The details of actually implementing this kind of HA fail-over on Linux or other
### Network Controller API
-The controller API is hosted via the same JSON API endpoint that ZeroTier One uses for local control (usually at 127.0.0.1 port 9993). All controller options are rounded under the */controller* base path.
+The controller API is hosted via the same JSON API endpoint that ZeroTier One uses for local control (usually at 127.0.0.1 port 9993). All controller options are routed under the `/controller` base path.
The controller microservice does not implement any fine-grained access control (authentication is via authtoken.secret just like the regular JSON API) or other complex mangement features. It just takes network and network member configurations and reponds to controller queries. We have an enterprise product called [ZeroTier Central](https://my.zerotier.com/) that we host as a service (and that companies can license to self-host) that does this.