On Tue, Aug 6, 2013 at 4:17 PM, Daniel Pittman <notifications@github.com>wrote:

> In lib/razor/cli/client.rb:
>
> > +      OptionParser.new do |opts|
> > +        opts.banner = "Usage: razor [command] [options...]\n"
> > +                      "   or: razor shell"
> > +        options[:verbose] = false
> > +        opts.on "-v", "--verbose", "Increases verbosity" do
> > +          options[:verbose] = true
> > +        end
> > +
> > +        options[:dump] = false
> > +        opts.on "-d", "--dump", "Dumps API output to the screen" do
> > +          options[:dump] = true
> > +        end
> > +
> > +        opts.on "-u", "--url URL", "Specify Razor API URL" do |rz_url|
> > +          options[:url] = rz_url
> > +        end
>
>  I actually disagree on this one ... people might deploy Razor in lots of
> interesting ways (i.e., behind proxies, mapped to fun places in the URL
> hierarchy etc.) We should therefore ask for the API entrypoint URL in its
> full glory instead of assuming where on a server it is.
> I am fine with the idea of asking for *the complete URL* rather than just
> the server and port; if we just ditch the magic that turns `localhost` into
> a valid URL, we are good to go IMO. (Eventually, I predict a `~/.razorrc`
> file to allow users to configure this away from the command line, but for
> now, just in the environment is fine. :)
>

Yes, definitely the complete URL - the client should not do anything beyond
using the supplied URL (and complaining when that use fails)

And I agree that eventually, we might add some sort of convenience like a
.razorrc ... but for now, that's not needed.

David