Andrea Campi
Andrea Campi
+1 on this, will it be merged?
+1 Another option would be to commit a CocoaPod spec to your repo.
See pull request #198
I should be able to reproduce pretty easily, but I'll let you know if I need more info. Thanks for reporting these bugs, appreciate it!
Uhm OK, just forwarding the port is not going to work either: the router is not going to like that. Besides, my goal is to have a "preview" that is...
Hey Chris, can you try now? Note that I've kind of deprecated port 9022 for the CC API; you should use port 9080. See single-node/README.md.
See this comment: https://github.com/cloudfoundry/vmc-lib/commit/5148d6c68668413303e7d8cc8c286130b9cc8db5#commitcomment-2577769 The attached log was captured a week ago with the then-latest version of vmc. > it looks like you have a redirect without a port Agreed,...
More details: AFAICT the CC (at least the legacy CC) generates redirects using standard Rails conventions; that is, using the port the request came in, as conveyed by Rack env...
Adding: ``` proxy_set_header X-Forwarded-Host $host:9080; ``` to the nginx router config fixed the issue for me, as long as the CC is only accessed on port 9080. That's acceptable for...
Can you try again now? One caveat with 0.5.x: vmc register does not work, see https://github.com/cloudfoundry/vmc/issues/59