Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: rdowner <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-79-brooklyn-docs@git.apache.org>
In-Reply-To: <git-pr-79-brooklyn-docs@git.apache.org>
Subject: [GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...
Content-Type: text/plain
Message-Id: <20160621111915.003C7E020A@git1-us-west.apache.org>
Date: Tue, 21 Jun 2016 11:19:14 +0000 (UTC)
archived-at: Tue, 21 Jun 2016 11:19:16 -0000

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

    https://github.com/apache/brooklyn-docs/pull/79#discussion_r67850130
  
    --- Diff: guide/ops/starting-stopping-monitoring.md ---
    @@ -0,0 +1,66 @@
    +---
    +title: Starting, Stopping and Monitoring
    +layout: website-normal
    +---
    +
    +**NOTE:** This document is for information on starting an Apache Brooklyn
    +Server.  For information on using the Brooklyn Client CLI to access an already
    +running Brooklyn Server, refer to [Client CLI Reference](cli/index.html).
    +
    +
    +## Starting
    +
    +To launch Brooklyn, from the directory where Brooklyn is unpacked, run:
    +
    +{% highlight bash %}
    +% bin/brooklyn launch > /dev/null 2>&1 & disown
    --- End diff --
    
    @aledsage My opinion is that this page serves a different purpose to the CLI reference page and we should keep both. This is duplicating a just a few lines, and then sending the reader to the Server CLI page. I think this is the smallest possible amount of duplication that keeps both pages useful.


---
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.
---