brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <>
Subject [GitHub] brooklyn-docs pull request #79: Ops guides updates for monitoring and disk s...
Date Tue, 21 Jun 2016 08:49:39 GMT
Github user aledsage commented on a diff in the pull request:
    --- Diff: guide/ops/ ---
    @@ -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 --
    Looking more closely, I see that the server-cli-reference doesn't have a good "stop" section.
Where do you think is most appropriate to put your new section on stopping? (bearing in mind
we'll need two variants: one for this approach, and one for rpm/deb packages).

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 or file a JIRA ticket
with INFRA.

View raw message