jschorr

8 ms·

31.
by jschorr 5y ago
Hi Nick, In the case of Authzed, we provide a gRPC API [0] which can be used from any application or language that supports gRPC, as well as designed client libraries for specific languages [1] to make integration even easier. Applications
32.
by jschorr 6y ago
In theory, you could provide an auth header representing your incoming user to our API and verify that way, yes. You'd still need to perform authentication (using Auth0 right now, as that is what ShareWith uses) to identify which user
33.
by jschorr 6y ago
For now, some form of proxy is required (unless your application supports OIDC already, in which case, you can just point it to our OIDC endpoint), but we are currently investigating ways to streamline this process even further. Stay tuned!
34.
by jschorr 6y ago
We've actually integrated with our Kubernetes ingress to protect our own dashboards via ShareWith. Right now, our "Usage" tab shows how to setup oauth proxy or use via OIDC directly, but we're looking into expanding the
35.
by jschorr 6y ago
Not at all! I thought I'd just give some interesting background info and not so subtly ask people to contribute to the project :D
36.
by jschorr 6y ago
(Co-founder of Quay here) Scalability and garbage collection are actually two of the main areas of focus Quay has had since its inception. As you mentioned, most modern Docker registries such as Quay and Harbor will automatically redirect t
37.
by jschorr 7y ago
I've always pronounced it "kway" but so long as its being used, I'm fine with any of the pronunciations :) Disclaimer: Named, cofounded, and now engineering lead of Quay
38.
by jschorr 9y ago
Yeah, I figured as much. Just thought it would be fun to add a bit more history, in case some found it interesting. Did not mean to imply that your article was incorrect :)
39.
by jschorr 9y ago
Some interesting history of source maps: They actually are older than the article suggests, having been original developed and used internally at Google starting in early 2009. At the time, Google had some of the largest applications writte
40.
by jschorr 10y ago
Disclaimer: I'm one of the engineers on the Quay team Quay doesn't (yet) support the idea of multi-step builds, but it is definitely on our roadmap. One recommended approach would be to make use of our squashed image support [1].
41.
by jschorr 11y ago
This space is still (fairly) new, so the general answer seems to be that there are multiple solutions to each problem, some that work well with others and some that do not. For orchestration, offhand the most active projects seem to be Kube
42.
by jschorr 11y ago
Also a good list of developers and devops people not getting any sleep tonight :-/
43.
by jschorr 11y ago
Latest Update from http://status.aws.amazon.com/ : 1:52 AM PDT We are actively working on the recovery process, focusing on multiple steps in parallel. While we are in recovery, customers will continue to see elevated error
44.
by jschorr 11y ago
It appears EC2 is affected as well now: 12:51 AM PDT We are investigating increased error rates for the EC2 APIs and launch failures for new EC2 instances in the US-EAST-1 Region.
45.
by jschorr 12y ago
1) Deploy images vs Dockerfiles is always a tradeoff. If you want to be absolutely sure that your code will run in production, then testing locally and pushing the image to a private registry such as Quay.io (disclaimer: I'm a cofounde
46.
by jschorr 13y ago
Offhand, the major benefits for your use case seem to be: - Speed and Flexibility: Extremely quick turn around time from development to production; Docker images usually start in under 10s and multiple images can be run concurrently. If a u
47.
by jschorr 13y ago
Here is an article my cofounder wrote giving some background and basic terminology: https://medium.com/devops-programming/7f5fd023158f
48.
by jschorr 13y ago
In the meantime, if you need to get it working right now, you can build your own binary as outlined here: http://blog.devtable.com/2014/01/using-docker-on-osx-with-pr... We've confirmed the instructions still
49.
by jschorr 14y ago
It is one of the peephole optimizations that Closure Compiler performs to save some space (read: 2-3 characters) in the final output: http://code.google.com/p/closure-compiler/source/browse/src/... . The compiler actually has a lot of cool
50.
by jschorr 15y ago
However, you can embed extra metadata for your specific source language if you wish, via the extension mechanism. Debug tools can then read the metadata in to do extra neat kinds of mapping (such as collapsing "native" stack frames).