DNS to StackInABox mapping...

[BenjamenMeyer]

Typically a StackInABoxService is mapped to a URL such as https://localhost/<servicename>/; however, sometimes it might be helpful to hap the StackInABoxService to just the DNS, such as https://<servicename> or https://<servicename>.localhost.

The current method is rather built-in to how StackInABox currently functions. It shouldn't be hard to add support for the other methods too; but it will require some additional support in stackinabox.util so the DNS names can be mapped, as well as an update to the routing to be able to support sending either one to a given StackInABoxService instance - thereby making both forms available.

This should also make it easier to support some services, like AWS, where the tools (e.g boto, botocore, boto3) have the DNS names more hard-coded into them.

[BenjamenMeyer]

This might be limited by the support utility (requests-mock, responses, and httpretty) that are directly supported...but we should still investigate to see if there is anything in StackInABox itself that would be a limiting factor too so that it could be supported if the utilities could make it happen.

requests-mock - this directly implements the Requests Adapter interfaces so in theory this may be the easiest to support in this manner.
httpretty - this might be the hardest
responses - not sure off hand, but it's probably somewhere in between the other two