The reason I mentioned both is to highlight that it's designed to be used
in both ways - as a CLI tool and as a Ruby library. I'd intended on writing
up some documentation on how to use it as a library too, but in fairness
this is outside of our MVP -- what's your take on that?

If we're not going to document how to use it as a library, I say we pull
back the docs to talk just about it being a CLI tool.

'Gem' in my mind is equivalent to saying 'Deb' or 'RPM' -- it doesn't
describe what's inside.



On Wed, Mar 5, 2014 at 9:15 AM, Anna Shipman <notifications@github.com>wrote:

> In README.md:
>
> >
> > -vCloud Edge Gateway is a tool that supports automated provisiong of a VMware vCloud Edge Gateway. It depends on [vCloud Core](https://github.com/alphagov/vcloud-core) and uses Fog under the hood.
> > +vCloud Edge Gateway is a tool and Ruby library that supports automated
>
> Maybe 'gem' instead of 'tool and Ruby library'?
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/alphagov/vcloud-edge_gateway/pull/20/files#r10292065>
> .
>