On Thu, Aug 19, 2010 at 10:31 PM, J Chris Anderson <jch...@apache.org> wrote:
>
> On Aug 19, 2010, at 1:25 PM, Jason Smith wrote:
>
>> On Fri, Aug 20, 2010 at 02:28, J Chris Anderson <jch...@apache.org> wrote:
>>
>>> KEY POINT: Any CouchApp which is designed to require vhosts is
>>> automatically not capable of running on localhost.
>>>
>>> Until we solve this issue I'm not much interested in refining the existing
>>> vhost stuff.
>>>
>>
>> Many apologies but I'm having trouble following. Why can't a couchapp run on
>> localhost? Already you can vhost localhost:5984 to your app's rewriter. Is
>> the problem because that locks you out of Futon? (localhost.localdomain:5984
>> still work, as does machine_name.local on OSX or Ubuntu, or if you've
>> installed Avahi or Bonjour)
>>
>
> I'm not that fancy.
>
> My point is that if you have an app that requires a vhost to work, then you
> have to do some machine level configuration to get more than one (or maybe 2)
> vhosts, from a standard issue Mac or Windows box. You can't ask grandma to do
> that.
>
> If the vhost directive allowed matching on parts of the path, then you could
> have */foobar = /foo/_design/bar/_rewrite and then the user could just visit
> localhost:5984/foobar and have it work.
>
> I described this in more detail here
> https://issues.apache.org/jira/browse/COUCHDB-230
>
> Because all the configuration happens in the couch, the couchapp can self
> configure. As soon as you start requiring people who don't know what a URL is
> to edit /etc/hosts, you're hosed.
>
> Chris
>
>
updated the ticket.
