diff --git a/docs/_build/doctrees/architecture.doctree b/docs/_build/doctrees/architecture.doctree index bdade63a8..f19b177e1 100644 Binary files a/docs/_build/doctrees/architecture.doctree and b/docs/_build/doctrees/architecture.doctree differ diff --git a/docs/_build/doctrees/environment.pickle b/docs/_build/doctrees/environment.pickle index e1bab18dd..2142dc41c 100644 Binary files a/docs/_build/doctrees/environment.pickle and b/docs/_build/doctrees/environment.pickle differ diff --git a/docs/_build/doctrees/server-installation.doctree b/docs/_build/doctrees/server-installation.doctree index 655312fda..54d489492 100644 Binary files a/docs/_build/doctrees/server-installation.doctree and b/docs/_build/doctrees/server-installation.doctree differ diff --git a/docs/_build/doctrees/ui-reference.doctree b/docs/_build/doctrees/ui-reference.doctree index 10c0e759a..fc9c6b410 100644 Binary files a/docs/_build/doctrees/ui-reference.doctree and b/docs/_build/doctrees/ui-reference.doctree differ diff --git a/docs/_build/html/_sources/architecture.rst.txt b/docs/_build/html/_sources/architecture.rst.txt index 34292cef9..8b8f9bde0 100644 --- a/docs/_build/html/_sources/architecture.rst.txt +++ b/docs/_build/html/_sources/architecture.rst.txt @@ -107,7 +107,7 @@ The check in process is what allows Netmaker to create dynamic mesh networks. As Database (sqlite, rqlite, postgres) ------------------------------------- -As of v0.8, Netmaker uses sqlite by default as a database. It can also use PostgreSQL, or rqlite, a distributed (RAFT consensus) databaseand. Netmaker interacts with this database to store and retrieve information about nodes, networks, and users. +As of v0.8, Netmaker uses sqlite by default as a database. It can also use PostgreSQL, or rqlite, a distributed (RAFT consensus) database. Netmaker interacts with this database to store and retrieve information about nodes, networks, and users. Additional database support (besides sqlite and rqlite) is very easy to implement for special use cases. Netmaker uses simple key value lookups to run the networks, and the database was designed to be extensible, so support for key-value stores and other SQL-based databases can be achieved by changing a single file. diff --git a/docs/_build/html/_sources/ui-reference.rst.txt b/docs/_build/html/_sources/ui-reference.rst.txt index 98a8b661c..d241cbce2 100644 --- a/docs/_build/html/_sources/ui-reference.rst.txt +++ b/docs/_build/html/_sources/ui-reference.rst.txt @@ -42,8 +42,8 @@ Edit **NOTE:** With the exception of Address Ranges (1-2) any setting that affects nodes will not take effect on existing nodes. It will only set the settings on any **new** node, after the setting has been changed. -(1) **Address Range (ipv4): The ipv4 private network CIDR. If edited, Netmaker will go through all nodes and update private addresses based on the new range.** -(2) **Address Range (ipv6): The ipv6 private network CIDR. If edited, Netmaker will go through all nodes and update private addresses based on the new range.** +(1) **Address Range (ipv4):** The ipv4 private network CIDR. If edited, Netmaker will go through all nodes and update private addresses based on the new range.** +(2) **Address Range (ipv6):** The ipv6 private network CIDR. If edited, Netmaker will go through all nodes and update private addresses based on the new range.** (3) **Local Range:** Only relevant if "Is Local" was switched on during creation. Specifies the local range that nodes will base their Endpoint off of (note: if a node cannot find an enpoint within the range it will fallback to public ip). (4) **Display Name:** The display name of the network. Network Name cannot be changed (acts as a unique ID) but display name can be changed. Only effects appearance in UI. (5) **Default Interface:** The default network interface name configured on each node. This defaults to "nm-". diff --git a/docs/_build/html/about.html b/docs/_build/html/about.html index 42ec1b53b..cbe7d2074 100644 --- a/docs/_build/html/about.html +++ b/docs/_build/html/about.html @@ -285,49 +285,56 @@
  • - Advanced Server Installation + Ingress + External Clients
  • - Integrating OAuth + Egress Gateway
  • - Client Installation + Relay Servers
  • - Ingress + External Clients + Kubernetes
  • - Egress Gateway + Advanced Server Installation
  • - Relay Servers + Advanced Client Installation + + +
    • +
  • + + + Integrating OAuth
  • - Using Netmaker + External Guides
    • diff --git a/docs/_build/html/architecture.html b/docs/_build/html/architecture.html index 5b8b554ba..c5737c6aa 100644 --- a/docs/_build/html/architecture.html +++ b/docs/_build/html/architecture.html @@ -57,7 +57,7 @@ - + @@ -209,7 +209,7 @@
  • - 1. About + About
    • @@ -329,49 +329,56 @@
  • - Advanced Server Installation + Ingress + External Clients
  • - Integrating OAuth + Egress Gateway
  • - Client Installation + Relay Servers
  • - Ingress GW + External Clients + Kubernetes
  • - Egress Gateway + Advanced Server Installation
  • - Relay Servers + Advanced Client Installation + + +
    • +
  • + + + Integrating OAuth
  • - Using Netmaker + External Guides
    • @@ -549,7 +556,7 @@

    NetclientDatabase (sqlite, rqlite, postgres)

    -

    As of v0.8, Netmaker uses sqlite by default as a database. It can also use PostgreSQL, or rqlite, a distributed (RAFT consensus) databaseand. Netmaker interacts with this database to store and retrieve information about nodes, networks, and users.

    +

    As of v0.8, Netmaker uses sqlite by default as a database. It can also use PostgreSQL, or rqlite, a distributed (RAFT consensus) database. Netmaker interacts with this database to store and retrieve information about nodes, networks, and users.

    Additional database support (besides sqlite and rqlite) is very easy to implement for special use cases. Netmaker uses simple key value lookups to run the networks, and the database was designed to be extensible, so support for key-value stores and other SQL-based databases can be achieved by changing a single file.

    @@ -640,7 +647,7 @@

    Limitations