Hi Doug,
I was the one asking this same question earlier in the thread you
linked.
What I ended up doing (or rather, what I am still in the process of
implementing) was to run my webapp on a separate server from Shindig,
but with a rewrite rule on my webapp server to my Shindig server.
e.g. http
Try removing :${SERVER_PORT}
from defaultShindigProxyConcatAuthority, defaultShindigTestHost
and anywhere else you might see a hard-coded port in your container.js.
Hi,
I've been eager to make use of the common container js since it was
introduced a few months ago, but my attempts thus far to use it have been
met with miscellaneous errors, where, as soon as I figure one out, there is
another waiting in line. With no examples or documentation, it's hard for me
