Nonintuitive config for /api not at server root #158
Description
My aptly api is behind a reverse proxy that exposes it at http://example.com:8888/aptly/api. After a lot of fiddling, I was able to get aptly_cli to eventually connect to it. Unfortunately, the behavior is non intuitive because of the way the base uri is constructed:
https://github.com/sepulworld/aptly_cli/blob/master/lib/aptly_command.rb#L55
Instead of having a config file with:
:servername: example.com/aptly
:port: 8888
it was necessary to specify the config as:
:servername: example.com
:port: 8888/aptly
It seems like an extra optional configuration argument that specifies the root prefix (/aptly) or constructing the base url in a different way that recognizes example.com/aptly and inserts the port after .com would be helpful.