jacobwg

9 ms·

91.
Vercel Secure Compute(vercel.com)
2 points by jacobwg 3y ago|0 comments
92.
Security in Vercel's front end cloud(vercel.com)
4 points by jacobwg 3y ago|0 comments
93.
by jacobwg 4y ago
Travis CI got acquired by Idera in 2019 ( https://news.ycombinator.com/item?id=18978251 ) then a month later laid off senior engineer staff ( https://news.ycombinator.com/item?id=19218036 ).
94.
by jacobwg 4y ago
Nice, yeah let me know if you want to chat further, feel free to send an email to jacob@depot.dev or the address in my profile. It would be really useful for us to know more about how you have things structured in GCP, etc.
95.
by jacobwg 4y ago
The docs can be improved, but here's the GitHub Actions guide: https://depot.dev/docs/integrations/github-actions The most important bit though is that we have a `depot/build-push-action` that implements
96.
by jacobwg 4y ago
We actually briefly entertained the idea of adding GitHub Runners as well. :) Perhaps someday, but we have a long way to go just on just Docker / containers. Just to note, you can totally use Depot within your GitHub Actions runs, even
97.
by jacobwg 4y ago
We have two ways at the moment: 1. If you need an uncached individual build, you can pass the `--no-cache` flag to build everything from scratch 2. We have a "clear all cache" button in our UI and CLI command, to wipe the entire p
98.
by jacobwg 4y ago
This is good advice! > Use Docker layer caching on GitHub Actions or your favorite CI ( https://evilmartians.com/chronicles/build-images-on-github-a... ) Since the time that article was written, BuildKit added native
99.
by jacobwg 4y ago
Today we're vertically scaling builders, so multiple builds run on the same large EC2 instance. The instances support processing multiple Docker builds at once, and thanks to BuildKit can even deduplicate work between multiple parallel
100.
by jacobwg 4y ago
Super cool, if you'd ever like to chat, let me know, my email is in my profile. We have an API in private beta to dynamically manage namespaces and acquire BuildKit connections within those namespaces, designed for platforms that need
101.
by jacobwg 4y ago
I haven't used Azure DevOps scale sets, but it looks similar, assuming it is orchestrating a persistent cache disk. If you're not using Azure DevOps, or even if you are, you can use `depot build` from any CI provider or from your
102.
by jacobwg 4y ago
We'd like to expand to support GCP as well yes. Are you looking to run the Depot runners in your own GCP account?
103.
by jacobwg 4y ago
So we have the concept of a "project", which in retrospect isn't the best name and is way too vague. :) But on our end, a "project" equates to one or two cache SSDs + one or two EC2 instances we're running, dep
104.
by jacobwg 4y ago
Potentially - if Nix or Bazel has already built the binaries, and just needs to construct an OCI-compliant image tarball with them, that can be quite quick, similar to a Dockerfile with only COPY instructions. Nix and Bazel can also give yo
105.
by jacobwg 4y ago
Exactly, we effectively persist BuildKit's state directory, so it doesn't even need to tar and export any of the internal state or layer cache, it gets the same state volume for the next build. Today we're using vertical scal
106.
by jacobwg 4y ago
--mount=type=cache is awesome! One of the reasons we created Depot is that cache mounts aren't supported in GitHub Actions, since each CI run is entirely ephemeral, so the files saved in a cache mount aren't saved across runs. Bui
107.
by jacobwg 4y ago
Yes, all the layer cache is saved on a persistent volume that's reused between jobs. In that respect, it's very similar to running `docker build` on your local laptop, where each build is incremental. But in Depot's case, tha
108.
by jacobwg 4y ago
Hey, I'll look into this one - this kind of error usually means that the BuildKit server believes the build has finished, but the CLI missed the fact that the build ended. It _might_ be related to your Rust build, but I want to make su
109.
by jacobwg 4y ago
Hey, we support that exact thing, the `depot` CLI wraps buildx so we support the same `--platform` flag. The difference between Depot and doing it directly in GitHub Actions is the "native CPU" part - on GitHub Actions, the Arm bu
110.
by jacobwg 4y ago
Hey! This is cryptominer protection - we used to have an option to access a trial without a credit card, and the cryptominers did indeed sign up. :) Requiring a credit card for the free tier is a speed bump for that, on the free plan it sub
111.
by jacobwg 4y ago
> What happens when GitHub adds native arm support though? That will make it much faster to build arm images on GHA natively - in that scenario, Depot should still be several times faster like we are on Intel today, primarily due to how
112.
by jacobwg 4y ago
> could somebody avoid the traditional `docker build` with say NixOS or Bazel Yes! You can think of an OCI image as a special kind of tarball, so things like NixOS and Bazel are able to construct that same tarball, potentially fairly qui
113.
Launch HN: Depot (YC W23) – Fast Docker Builds in the Cloud
224 points by jacobwg 4y ago|92 comments
114.
by jacobwg 4y ago
For me, the happy medium is an extension that replaces thumbnails with a frame from the actual video itself ( https://chrome.google.com/webstore/detail/clickbait-remover-... ). Videos are still visually identifiable
115.
by jacobwg 4y ago
The version installable with Homebrew is working for me on Ventura / M1. I have an occasional issue where one of my external displays switches from 60 Hz to 40 Hz, and I use displayplacer to toggle the refresh rate to reset the monitor
116.
by jacobwg 4y ago
Anecdotally, this is starting to shift with M1 MacBooks, Graviton is looking more attractive for precisely that architecture parity reason for teams using majority M1 devices.
117.
by jacobwg 4y ago
Agreed, this is more or less the inspiration behind Depot ( https://depot.dev ). Today it builds Docker images with this philosophy, but we'll be expanding to other more general inputs as well. Builds get routed to runner ins
118.
Protobuf-ES: Protocol Buffers TypeScript/JavaScript runtime(buf.build)
205 points by jacobwg 4y ago|183 comments
119.
Next.js 13(nextjs.org)
229 points by jacobwg 4y ago|100 comments
120.
Turbopack – The Successor to Webpack(turbo.build)
12 points by jacobwg 4y ago|1 comments

More ›