Remove obsolete Rack/Passenger/WEBrick deployment references

OpenVox Server 8.x runs on JRuby (puppetserver) only; the Rack
application deployment model (config.ru with Passenger/Apache or
WEBrick) no longer exists. Remove the stale inline references:

- Drop the three config.ru/Rack `> **Note:**` blocks in dirs_vardir,
  dirs_confdir, and dirs_codedir.
- Reword the config_print bullet to drop the Rack/Passenger/config.ru
  framing while keeping the non-standard confdir/vardir guidance.
- Simplify the static_catalogs sentence to drop the obsolete
  Ruby/WEBrick/Passenger master reference.
- Drop the "(or your Rack server)" aside in config_important_settings.

Closes #275

Signed-off-by: Michael Harp <mike@mikeharp.com>

Author: miharp

docs/_openvox_8x/config_important_settings.markdown

@@ -125,7 +125,7 @@ These settings should usually go in `[server]`. However, if you're using Puppet
 ### Basics
 
 * [`dns_alt_names`][dns_alt_names] --- A list of hostnames the server is allowed to use when acting as an OpenVox Server. The hostname your agents use in their `server` setting **must** be included in either this setting or the master's `certname` setting. Note that this setting is only used when initially generating the OpenVox Server's certificate --- if you need to change the DNS names, you must:
-    1. Turn off the Puppet server service (or your Rack server).
+    1. Turn off the Puppet server service.
     2. Run `sudo puppetserver ca clean --certname <SERVER'S CERTNAME>`.
     3. Run `sudo puppetserver ca generate --certname <SERVER'S CERTNAME> --subject-alt-names <ALT NAME 1>,<ALT NAME 2>,...`.
     4. Re-start the Puppet server service.

docs/_openvox_8x/config_print.markdown

@@ -78,7 +78,7 @@ To see the settings the OpenVox Server service would use:
 * Specify `--section server`.
 * Use the `--environment` option to specify the environment you want settings for, or let it default to `production`.
 * Remember to use `sudo`.
-* If your OpenVox Server is managed as a rack application (e.g. with Passenger), check the `config.ru` file to make sure it's using the [confdir][] and [vardir][] that you expect. If it's using non-standard ones, you will need to specify them on the command line with the `--confdir` and `--vardir` options; otherwise you might not see the correct values for settings.
+* If your OpenVox Server uses a non-standard [confdir][] or [vardir][], specify them on the command line with the `--confdir` and `--vardir` options; otherwise you might not see the correct values for settings.
 
 ### Examples
 

docs/_openvox_8x/dirs_codedir.markdown

@@ -20,8 +20,6 @@ When Puppet is running as either root, a Windows user with administrator privile
 
 The system codedir is what you usually want to use, since you will usually run Puppet's commands and services as root or `puppet`. (Note that admin commands like `puppet module` must be run with `sudo` to use the same codedir as OpenVox agent or OpenVox Server.)
 
-> **Note:** When OpenVox Server is running as a Rack application, the `config.ru` file must explicitly set `--codedir` to the system codedir. The example `config.ru` file provided with the Puppet source does this.
-
 ### Configuration
 
 The location of the codedir can be configured in puppet.conf with [the `codedir` setting][codedir], but note that Puppet Server doesn't use that setting; it has its own `jruby-puppet.master-code-dir` setting [in puppetserver.conf][puppetserver_conf]. If you're using a non-default codedir, _you must change both settings._

docs/_openvox_8x/dirs_confdir.markdown

@@ -21,8 +21,6 @@ The system confdir is what you usually want to use, since you will usually run P
 services as root or `puppet`. (Note that admin commands like `puppetserver ca` must be run with `sudo`
 to use the same confdir as OpenVox agent or OpenVox Server.)
 
-> **Note:** When OpenVox Server is running as a Rack application, the `config.ru` file must explicitly set `--confdir` to the system confdir. The example `config.ru` file provided with the Puppet source does this.
-
 ### Configuration
 
 Puppet's confdir can be specified on the command line with the `--confdir` option, but it can't be set

docs/_openvox_8x/dirs_vardir.markdown

@@ -24,8 +24,6 @@ The system cache directory is what you usually want to use, since you will usual
 and services as root or `puppet`. (Note that admin commands like `puppetserver ca` must be run with
 `sudo` to use the same directories as OpenVox agent or OpenVox Server.)
 
-> **Note:** When OpenVox Server is running as a Rack application, the `config.ru` file must explicitly set `--vardir` to the system cache directory. The example `config.ru` file provided with the Puppet source does this.
-
 ### Configuring the location of the cache directory
 
 You can specify Puppet's cache directory on the command line by using the `--vardir` option, but you can't set it in `puppet.conf`. If `--vardir` isn't specified when a Puppet application is started, it will always use the default cache directory location.

docs/_openvox_8x/static_catalogs.md

@@ -117,7 +117,7 @@ The script's standard output becomes the file's `code_content`, provided the scr
 Starting in Puppet 4.4 and OpenVox Server 2.3.0, the global `static_catalogs` setting is enabled by default, whether you upgrade Puppet or perform a clean installation.
 However, the default configuration doesn't include the `code-id-command` and `code-content-command` scripts or settings needed to produce static catalogs, and even when configured to produce static catalogs OpenVox Server doesn't inline metadata for all types of file resources.
 
-Static catalogs are produced only by OpenVox Server. The Ruby OpenVox server never produces static catalogs, even when served by WEBrick or Passenger.
+Static catalogs are produced only by OpenVox Server.
 
 OpenVox Server also won't produce static catalogs for an agent under the following circumstances: