brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sjcorb...@apache.org
Subject [1/2] brooklyn-docs git commit: Fix broken links to SSH keys docs
Date Thu, 30 Jun 2016 16:28:54 GMT
Repository: brooklyn-docs
Updated Branches:
  refs/heads/master 9f2f0cf35 -> ed10f420b


Fix broken links to SSH keys docs


Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/d922f5a9
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/d922f5a9
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/d922f5a9

Branch: refs/heads/master
Commit: d922f5a9f000a90b53e9a659231ed8c831da1e61
Parents: 9f2f0cf
Author: Mike Zaccardo <mike.zaccardo@cloudsoftcorp.com>
Authored: Wed Jun 29 12:49:03 2016 -0700
Committer: Mike Zaccardo <mike.zaccardo@cloudsoftcorp.com>
Committed: Wed Jun 29 12:49:03 2016 -0700

----------------------------------------------------------------------
 guide/ops/locations/_byon.md      | 2 +-
 guide/ops/locations/_clouds.md    | 2 +-
 guide/ops/locations/_localhost.md | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d922f5a9/guide/ops/locations/_byon.md
----------------------------------------------------------------------
diff --git a/guide/ops/locations/_byon.md b/guide/ops/locations/_byon.md
index 38f6595..a7ab71b 100644
--- a/guide/ops/locations/_byon.md
+++ b/guide/ops/locations/_byon.md
@@ -13,7 +13,7 @@ Your nodes must meet the following prerequisites:
 
 - A suitable OS must have been installed on all nodes
 - The node must be running sshd (or similar)
-- the brooklyn user must be able to ssh to each node as root or as a user with passwordless
sudo permission. (For more information on SSH keys, see [here](ssh-keys.html).) 
+- the brooklyn user must be able to ssh to each node as root or as a user with passwordless
sudo permission. (For more information on SSH keys, see [here](#ssh-keys).) 
 
 To deploy to machines with known IP's in a blueprint, use the following syntax:
 

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d922f5a9/guide/ops/locations/_clouds.md
----------------------------------------------------------------------
diff --git a/guide/ops/locations/_clouds.md b/guide/ops/locations/_clouds.md
index 4072a1a..24b92d0 100644
--- a/guide/ops/locations/_clouds.md
+++ b/guide/ops/locations/_clouds.md
@@ -154,7 +154,7 @@ For more keys and more detail on the keys below, see
 - Private keys can be specified using `privateKeyFile`; 
   these are not copied to provisioned machines, but are required if using a local public
key
   or a pre-defined `authorized_keys` on the server.
-  (For more information on SSH keys, see [here](ssh-keys.html).) 
+  (For more information on SSH keys, see [here](#ssh-keys).) 
 
 - If there is a passphrase on the key file being used, you must supply it to Brooklyn for
it to work, of course!
   `privateKeyPassphrase` does the trick (as in `brooklyn.location.jclouds.privateKeyPassphrase`,
or other places

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/d922f5a9/guide/ops/locations/_localhost.md
----------------------------------------------------------------------
diff --git a/guide/ops/locations/_localhost.md b/guide/ops/locations/_localhost.md
index 7ac906a..8743be5 100644
--- a/guide/ops/locations/_localhost.md
+++ b/guide/ops/locations/_localhost.md
@@ -20,7 +20,7 @@ brooklyn.location.localhost.privateKeyPassphrase=s3cr3tPASSPHRASE
 Alternatively, you can create a specific localhost location through the location wizard tool
available within the web console.
 This location will be saved as a [catalog entry]({{ site.path.guide }}/ops/catalog/index.html#locations-in-catalog)
for easy reusability.
 
-If you encounter issues or for more information, see [SSH Keys Localhost Setup](ssh-keys.html#localhost-setup).

+If you encounter issues or for more information, see [SSH Keys Localhost Setup](#localhost-setup).

 
 If you are normally prompted for a password when executing `sudo` commands, passwordless
`sudo` must also be enabled.  To enable passwordless `sudo` for your account, a line must
be added to the system `/etc/sudoers` file.  To edit the file, use the `visudo` command:
 {% highlight bash %}


Mime
View raw message