Added docker

Author: mikucionisaau

content/gui-reference/menu-bar/edit.md

@@ -10,5 +10,17 @@ The Edit menu offers a set of commands supported in the system editor. The items
   * **Copy:** places a copy of the selected text in the clipboard. There must be an active text selection.
   * **Paste:** places text in the clipboard at the cursor location in the currently active editor. There must be text in the clipboard, and an editor must be active.
   * **Delete:** delete selected text. There must be an active text selection.
+  * **Select all:** selects all text or all elements in the automaton.
+  * **Find:** searches for the text occurances *locally* and *globally* (`Control`+`Shift`+`F`)
+  * **Replace:** searches and replaces the text occurances *locally* and *globally* (`Control`+`Shift`+`R`)
   * **Insert Template:** adds a new empty template to the system description.
-  * **Remove Template:** removes the currently selected template from the system description. There must be a template selected.
+  * **Remove Template:** removes the currently selected template from the system description. There must be a template selected.
+  * **Engine:** selects the engine to connect to:
+    - `Bundled` is the `server` found in the UPPAAL installation directory (cannot be changed).
+    - `Remote` is the `sockerserver` process accepting and relaying commands on a remote machine using TCP/IP protocol. See [socketserver](/toolsandapi/socketserver) for more details on how to launch it.
+
+    Note that the GUI and server versions must match.
+  * **Engines...** invokes an engine connection dialog to edit the engine selection in the **Engine** menu.
+    The dialog allows to customize engine connections:
+     - Address and port number for the remote connection.
+     - Specific engine server commands, including remote server through `ssh`, e.g.:  `ssh bigmachine uppaal/bin/server`

content/toolsAndAPI/_index.md

@@ -13,5 +13,6 @@ chapter: true
 - Command line interface to verifier: [verifyta](verifyta)
 - Java model editor, simulator and verifier interface: [Java API](javaapi)
 - Connect GUI to a remote server via TCP/IP sockets: [socketserver](socketserver)
+- Running engine inside Docker: [docker](docker)
 - Document and trace file formats: [file formats](file-formats)
 - Including UPPAAL models into LaTeX publications: [LaTeX](latex)

content/toolsAndAPI/socketserver.md

@@ -3,29 +3,35 @@ title: Socketserver
 weight: 40
 ---
 
-To start a remote server, use the `socketserver` binary (included for Linux, SunOS and MacOS). To use a remote server, see the section on [command line options](/toolsandapi/uppaal/) for the GUI.
-
-The <tt>socketserver</tt> can be executed from the command line using one of the following commands:
-
-> <tt>socketserver [-p<P1>] [-s<P2>]</tt>  
-> <tt>socketserver -h</tt>
+To start a remote server, use the `socketserver` binary (included for Linux, macOS, SunOS).
+To use the remote server, see the section on [Edit > Engine](/gui-reference/menu-bar/edit/) for the GUI.
+
+The `socketserver` can be run from the command line on a remote machine using one of the following commands:
+
+```
+Synopsis:
+  socketserver [-n] [-p<P1>] [command]...
+  socketserver -h
+  h : Print this help screen
+  n : Run in native mode
+  p : Set port in server mode (default is 2350)
+  d : Write communication to debug files in current directory
+  m : Write communication standard out
+  [commmand] : A series of argv to execute as the server command
+```
 
 The available command line options are:
 
-<dl>
-
-<dt><tt>-h</tt></dt>
-
-<dd>Prints a brief description of the command line options.</dd>
-
-<dt><tt>-p</tt></dt>
-
-<dd>Set port in server mode (default is 2350).</dd>
+`-h`
+: Prints a brief description of the command line options.
 
-<dt><tt>-s</tt></dt>
+`-p`
+: Sets TCP/IP server port to listen to (default is 2350).
 
-<dd>Set filename of server binary to P2.</dd>
+`-d`
+: write the engine communication to debug files in the current directory (useful in debugging).
 
-</dl>
+`-m`
+: write the engine communication to standard output (usefull in debugging).
 
-The <tt>socketserver</tt> will load the <tt>server</tt> from the directory where it was invoked, and act as a proxy.
+The `socketserver` runs the `server` from the directory where it was invoked, and acts as a proxy on TCP/IP port.