Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: drigodwin <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-98-brooklyn-docs@git.apache.org>
In-Reply-To: <git-pr-98-brooklyn-docs@git.apache.org>
Subject: [GitHub] brooklyn-docs pull request #98: Improve location docs
Content-Type: text/plain
Message-Id: <20160802131344.41BBBE0007@git1-us-west.apache.org>
Date: Tue,  2 Aug 2016 13:13:44 +0000 (UTC)
archived-at: Tue, 02 Aug 2016 13:13:46 -0000

Github user drigodwin commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/98#discussion_r73151662
  
    --- Diff: guide/ops/locations/_localhost.md ---
    @@ -7,30 +7,41 @@ section_type: inline
     ### Localhost
     
     If passwordless ssh login to `localhost` and passwordless `sudo` is enabled on your 
    -machine, you should be able to deploy blueprints with no special configuration,
    +machine, you should be able to deploy some blueprints with no special configuration,
     just by specifying `location: localhost` in YAML.
     
     If you use a passpharse or prefer a different key, these can be configured as follows: 
     
    -{% highlight bash %}
    -brooklyn.location.localhost.privateKeyFile=~/.ssh/brooklyn_key
    -brooklyn.location.localhost.privateKeyPassphrase=s3cr3tPASSPHRASE
    -{% endhighlight %}
    +    location:
    +      localhost:
    +        privateKeyFile=~/.ssh/brooklyn_key
    +        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.
    --- End diff --
    
    This is now #locations-in-the-catalog


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---