Repository: brooklyn-docs
Updated Branches:
  refs/heads/master cceb1b84b -> cf63c03d7

Various fixes. Mainly changing relative links to absolute links


Branch: refs/heads/master
Commit: daec264e6f1dcc4bdd7cb3bc99db88d87e78cdf8
Parents: cceb1b8
Author: graeme.miller <>
Authored: Mon Sep 12 16:03:55 2016 +0100
Committer: graeme.miller <>
Committed: Tue Sep 20 11:01:01 2016 +0100

 guide/ops/               | 4 +---
 guide/ops/           | 2 +-
 guide/ops/                      | 4 ++--
 guide/ops/troubleshooting/          | 2 +-
 guide/ops/troubleshooting/ | 6 +++---
 guide/start/                         | 2 +-
 guide/yaml/                 | 2 +-
 guide/yaml/             | 2 +-
 guide/yaml/winrm/                      | 4 ++--
 9 files changed, 13 insertions(+), 15 deletions(-)
diff --git a/guide/ops/ b/guide/ops/
index 4ab9501..8a395c2 100644
--- a/guide/ops/
+++ b/guide/ops/
@@ -14,8 +14,6 @@ children:
 The file `~/.brooklyn/` is read when Brooklyn starts
 to load server configuration values.
-A different properties file can be specified either additionally or instead
-through [CLI options]({{ }}/ops/server-cli-reference.html).
 A template []({{brooklyn_properties_url_path}}) file is 
 with abundant comments.
@@ -57,7 +55,7 @@ More information, including setting up a certificate, is 
described [further belo
 Values in `` can use the Camp YAML syntax. Any value 
starting `$brooklyn:` is 
 parsed as a Camp YAML expression.
-This allows [externalized configuration](externalized-configuration.html) to 
be used from 
+This allows [externalized configuration]({{}}/ops/externalized-configuration.html) to be used from For example:
 {% highlight properties %}
diff --git a/guide/ops/ 
index 5cd69a8..8ae1e02 100644
--- a/guide/ops/
+++ b/guide/ops/
@@ -16,7 +16,7 @@ To install Apache Brooklyn on a production server:
 This guide covers the basics. You may also wish to configure:
-* [Logging](logging.html)
+* [Logging]({{ }}/ops/logging.html)
 * [Persistence](persistence/)
 * [High availability](high-availability/)
diff --git a/guide/ops/ b/guide/ops/
index a4c386a..b7c5cf5 100644
--- a/guide/ops/
+++ b/guide/ops/
@@ -35,7 +35,7 @@ There are three main consumers of disk space:
 * **Log files**: Brooklyn writes info and debug log files. By default, these 
   written to the local filesystem. This can be reconfigured to set the
   destination and to increase or decrease the detail in the logs. See the
-  [Logging](logging.html) section for more details.
+  [Logging]({{ }}/ops/logging.html) section for more details.
 The Apache Brooklyn distribution itself, when unpacked, consumes approximately
 75MB of disk space. This includes everything needed to run Brooklyn except for 
@@ -56,7 +56,7 @@ therefore, can consume up to 2GB of disk space.
 In the default configuration of Brooklyn's `.tar.gz` and `.zip` distributions,
 logs are saved to the Brooklyn installation directory. You will most likely 
-to [reconfigure Brooklyn's logging](logging.html) to save logs to a location
+to [reconfigure Brooklyn's logging]({{ }}/ops/logging.html) to 
save logs to a location
 elsewhere. In the `.rpm` and `.deb` packaging, logging files will be located
 under `/var/log`. You can further reconfiguring the logging detail level and 
 rotation according to your organisation's policy.
diff --git a/guide/ops/troubleshooting/ 
index 815d33c..ac00aeb 100644
--- a/guide/ops/troubleshooting/
+++ b/guide/ops/troubleshooting/
@@ -82,7 +82,7 @@ For example, it can show the exception stack trace in the 
thread that was execut
 ## Log Files
 Brooklyn's logging is configurable, for the files created, the logging levels, 
-See [Logging docs](../logging.html).
+See [Logging docs]({{ }}/ops/logging.html).
 With out-of-the-box logging, `` and `brooklyn.debug.log` 
files are created. These are by default 
 rolling log files: when the log reaches a given size, it is compressed and a 
new log file is started.
diff --git a/guide/ops/troubleshooting/ 
index 2b0716d..2168859 100644
--- a/guide/ops/troubleshooting/
+++ b/guide/ops/troubleshooting/
@@ -156,15 +156,15 @@ appropriate for a production server.
 If the Brooklyn Server was originally run to allow a remote debugger to 
connect (strongly 
 discouraged in production!), then this provides a convenient way to 
investigate why Brooklyn
-is being slow or unresonsive. See the Debugging Tips in the 
-tip [Debugging Remote Brooklyn][({{ 
+is being slow or unresponsive. See the Debugging Tips in the 
+tip [Debugging Remote Brooklyn]({{ 
 and the [IDE docs]({{ }}/dev/env/ide/) for more information.
 ## Log Files
 Apache Brooklyn will by default create and 
brooklyn.debug.log files. See the
-[Logging](({{ }}/ops/logging.html) docs for more information.
+[Logging]({{ }}/ops/logging.html) docs for more information.
 The following are useful log messages to search for (e.g. using `grep`). Note 
the wording of
 these messages (or their very presence) may change in future version of 
diff --git a/guide/start/ b/guide/start/
index 4dcc011..4b1be82 100644
--- a/guide/start/
+++ b/guide/start/
@@ -253,6 +253,6 @@ For details on the CLI, see the [Client CLI Reference]({{ }}/ops
 <div class="started-pdf-exclude">
-The first thing we want to do with Brooklyn is **[deploy a 
+The first thing we want to do with Brooklyn is **[deploy a blueprint]({{ }}/ops/blueprints.html)**.
diff --git a/guide/yaml/ b/guide/yaml/
index e9aa617..5acf4de 100644
--- a/guide/yaml/
+++ b/guide/yaml/
@@ -43,7 +43,7 @@ After the application has been deployed, you can ensure it is 
working as expecte
 * You can also use the Elasticsearch REST API to explore further. The 
Elasticsearch Cluster entity has a `urls.http.list` sensor. Using a host:port 
from that list you will be able to access the REST API. The following URL will 
give you the state of the cluster 
`http://<host:port>/_cluster/health?pretty=true`. As you can see the 
`number_of_nodes` is currently 2, indicating that the Elasticsearch nodes are 
communicating with each other.
 ### Interesting Feature Spotlight
-We will mainly focus on the Elasticsearch blueprint, and will be clear when 
another blueprint is being discussed. This blueprint describes a cluster of 
Elasticsearch nodes. Clustering is a useful technique that is explained in more 
depth [here](../clusters.html).
+We will mainly focus on the Elasticsearch blueprint, and will be clear when 
another blueprint is being discussed. This blueprint describes a cluster of 
Elasticsearch nodes. Clustering is a useful technique that is explained in more 
depth [here]({{}}/yaml/clusters.html).
 #### Provisioning Properties
 Our Elasticsearch blueprint has a few requirements of the location in which it 
is run. Firstly, it must be run on an Ubuntu machine as the example has been 
written specifically for this OS. Secondly, two ports must opened to ensure 
that the entities can be accessed from the outside world. Both of these 
requirements are configured via as follows:
diff --git a/guide/yaml/ 
index 538e2fe..b8f0240 100644
--- a/guide/yaml/
+++ b/guide/yaml/
@@ -41,7 +41,7 @@ such as for inheriting configuration from a parent entity.
 When defining an entity in the catalog, it can include configuration values 
like any other 
 blueprint. It can also explicitly declare config keys. For details of how to 
write and add
 catalog items, see [Catalog]({{ }}/ops/catalog/). For more 
details of 
-declaring config keys, see the section ["Declaring New Config Keys" in Custom 
+declaring config keys, see the [Custom Entities]({{ 
}}/yaml/custom-entities.html#declaring-new-config-keys) page.
 The example below illustrates the principles:
diff --git a/guide/yaml/winrm/ b/guide/yaml/winrm/
index e21494c..4e7b71b 100644
--- a/guide/yaml/winrm/
+++ b/guide/yaml/winrm/
@@ -70,7 +70,7 @@ A Sample Blueprint
 Creating a Windows VM is done using the 
`` entity type. 
This is very similar
 to `VanillaSoftwareProcess`, but adapted to work for Windows and WinRM instead 
of Linux. We suggest you read the
-[documentation for 
VanillaSoftwareProcess](../custom-entities.html#vanilla-software-using-bash) to 
find out what you
+[documentation for VanillaSoftwareProcess]({{ 
}}/yaml/custom-entities.html#vanilla-software-using-bash) to find out what you
 can do with this entity.
 Entity authors are strongly encouraged to write Windows Powershell or Batch 
scripts as separate 
@@ -127,7 +127,7 @@ Brooklyn source code]({{ site.brooklyn.url.git 
 Tips and Tricks
-The best practices for other entities (e.g. using 
+The best practices for other entities (e.g. using [VanillaSoftwareProcess]({{ }}/yaml/custom-entities.html#vanilla-software-using-bash))
 apply for WinRM as well.
 ### Execution Phases

Reply via email to