+1 On 24 March 2016 at 18:12, John McCabe <[email protected]> wrote:
> +1 Geoff > Having a CLI download alongside the brooklyn release as well makes sense, > like the web ui the user should be able to run the client from their local > machine to connect to a remote brooklyn instance (which is supported and > imho preferable since it keeps you off the server), bundling it only in the > release means the user has to either copy br from the node brooklyn is > running on or download a full brooklyn release only to get at the cli tool > which seems unnecessary. > I'd be inclined to package it (rpm, brew etc) separately as well - > installing the brooklyn rpm would pull in the client as a dep (will need to > be in a repo to make this painless). For a client install you could use > brew/port on OSX, possibly Chocolatey on Windows. > > On Thu, 24 Mar 2016 at 17:56 Geoff Macartney < > [email protected]> wrote: > > > I suggest adding the CLI artifacts to the release alongside the brooklyn > > zip. At the same time as the brooklyn zip is copied to the release > > location, get the CLI artifact out of the Maven repository, for good > > measure unpack it, and upload the individual builds of the CLI tool to > the > > same location. Then update docs to explain how to download it too. > > > > Remember the vagrant approach is really there as a Getting Started track, > > it’s not the typical path for using Brooklyn in anger. > > > > > > ———————————————————— > > Gnu PGP key - http://is.gd/TTTTuI > > > > > > > On 24 Mar 2016, at 17:51, Duncan Godwin < > [email protected]> > > wrote: > > > > > > Hi All, > > > > > > I've found a problem with the way the CLI is distributed for Brooklyn. > > It's > > > included in the release files which means when an initial user uses the > > > vagrant getting started guide, the CLI is inside the vagrant box, not > on > > > the users machine. As there's no download link to the CLI anywhere it > > means > > > the flow of the documentation no longer works. > > > > > > The solutions to this could be: > > > > > > * Add additional downloads for each of the CLI versions somewhere > > > * Extract the correct CLI from the vagrant box to the users machine in > > the > > > instructions > > > * Download the CLI bundle and extract and install the correct one > > > > > > What are everyone's thoughts? > > > > > > Many thanks > > > > > > Duncan > > > > >
