31–33 of 33 posts
Earlier quoted context omitted.
Sorry, you have to rebuild the top level representation, which I guess is now called a Pod.
No, Pod is designed for multi-containers grouped to run on the same host, primarily for sidekick process, like syslog. If you want to multi-host deployment, it is similar to CloudFormation. You can still use multiple pods to compose a distributed app.
Earlier quoted context omitted.
A 403 only works in the case that you have an all-or-nothing authentication scheme. A 403 for a resource that exists but is unauthorised leaks the information that the resource exists. Many Github customers don't want people to be able to guess at their private repos, and the 404 is the only code that is legitimately able to express the union of "not here" and "not here because you're not allowed to know it's here".
Not at all. If I have a private repo "foo" and a public repo "bar" and no others, given an unauth'd request: > request "foo" => 403 > request "bar" => 200 > request "baz" => 403 > request "qux" => 403 The unauth'd requester can't tell that foo exists and baz and qux do not.
The "hiding the existence of resources" purpose has to be carried by something. The RFC says it's carried by 404, and that's that.
As a very effective substrate for hosting containers, we at Terminal think a lot about which of the container mechanisms will win over the long term. My personal opinion is that the winner will be the group that successfully gets Enterprises to change their workload design. I also don't think that Rocket is necessarily a superior format to Docker, but I think they're both dealing with the recognition that any big cha…
See for example Garden (née Warden)[0][1], which is the basic building block of Cloud Foundry.
[0] https://github.com/cloudfoundry-incubator/garden [1] http://blog.pivotal.io/cloud-foundry-pivotal/features/cloud-...