more

SUMMARY.adoc

@@ -12,6 +12,8 @@
  {% endif %}
  .. link:topics/installation/directory-structure.adoc[Distribution Directory Structure]
  .. link:topics/openshift.adoc[Installing on OpenShift]
+ . link:topics/deployment-mode.adoc[Choosing a Deployment Mode]
+ .. link:topics/deployment-mode/standalone.adoc[Standalone Mode]
  . link:topics/cache.adoc[Server Cache]
  . link:topics/clustering.adoc[Clustering]
  . link:topics/proxy.adoc[Keycloak Security Proxy]

book.json

@@ -12,6 +12,10 @@
     "community": true,
     "product": false,
     "images": "rhsso-images",
+    "appserver": {
+      "name": "Wildfly",
+      "version": "10.0.0.Final"
+    },
     "project": {
       "name": "Keycloak",
       "version": "1.9.3.Final-SNAPSHOT"

topics/clustering.adoc

@@ -5,6 +5,7 @@ Keycloak doesn't replicate realms and users, but instead relies on all nodes usi
 This can be a relational database or Mongo.
 To make sure your database doesn't become a single point of failure you may also want to deploy your database to a cluster. 
 
+[[_clustering_db_lock]]
 === DB lock
 
 Note that Keycloak supports concurrent startup by more cluster nodes at the same.

topics/deployment-mode.adoc

@@ -0,0 +1,6 @@
+== Choosing a Deployment Mode
+
+Before deploying {{book.project.name}} in a production environment you need to decide which type of deployment method
+you are going to use.  Will you run {{book.project.name}} within a cluster?  Do you want a centralized way to manage
+your server configurations?  This is where deciding the deployment mode comes in.  This decision
+ effects how you configure databases, configure caching and even how you boot the server.

topics/deployment-mode/standalone.adoc

@@ -0,0 +1,20 @@
+=== Standalone Mode
+
+Standalone mode is only useful when you want to run one, and only one {{book.project.name}} server instance.  Standalone
+instances contain all the configuration files they need locally.  What this basically means is that any configuration done
+must be done on the config files contained in the installed distribution on the machine the {{book.project.name}} is going to run on
+{{book.project.name}} standalone mode is available pre-configured out of the box.  It turns off clustering entirely
+and turns any distributed caches into local-only ones.
+
+==== Standalone Boot Script
+
+When running the server in standalone mode, there is a specific script you need to run to boot the server depending on your
+operating system.  These scripts live in the _bin/_ directory of the server distribution.
+
+.Standalone Boot Scripts
+{% if book.product %}
+. image:../../rhsso-images/standalone-boot-files.png[alt="distribution"]
+{% endif %}
+{% if book.community %}
+image:../../keycloak-images/standalone-boot-files.png[alt="distribution"]
+{% endif %}

topics/installation/directory-structure.adoc

@@ -5,7 +5,8 @@ This chapter walks you through the directory structure of the server distributio
 .distribution directory structure
 {% if book.product %}
 . image:../../rhsso-images/files.png[alt="distribution"]
-{% else %}
+{% endif %}
+{% if book.community %}
 image:../../keycloak-images/files.png[alt="distribution"]
 {% endif %}
 

topics/installation/system-requirements.adoc

@@ -10,4 +10,4 @@ These are the requirements to run the {{book.project.name}} authentication serve
 * At least 1G of diskspace
 
 {{book.project.name}} can be clustered without multicast, but this requires a bunch of configuration changes.  Please see
-the <<fake/../../clustering.adoc#,clustering>> section of this guide for more information.
+the <<fake/../../clustering.adoc#_clustering_db_lock,clustering>> section of this guide for more information.