build-push-action
depot.ai
build-push-action | depot.ai | |
---|---|---|
3 | 3 | |
20 | 79 | |
- | - | |
6.8 | 8.1 | |
about 1 month ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
build-push-action
-
Launch HN: Depot (YC W23) – Fast Docker Images in the Cloud
I think that's along the lines of what you're describing as a Depot GitHub Action: https://github.com/depot/build-push-action.
-
Build all of your Docker images concurrently from a file with bake
Like our depot/build-push-action, you can use GitHub's OpenID Connect tokens via a trust relationship, so your builds can authenticate with Depot projects without needing any static access tokens. Here is an example GitHub Action workflow that builds images from a docker-bake.hcl file:
-
Show HN: Depot – fast, remote Docker container builds
It should be just as as straightforward with Depot as well - we have a depot/build-push-action (https://github.com/depot/build-push-action) that accepts the same inputs as docker/build-push-action to make it easy (under the hood, both use BuildKit).
steps:
depot.ai
- GitHub - depot/depot.ai: Embed machine learning models in your Dockerfile
- Depot.ai – Docker registry for public machine learning models
-
Show HN: depot.ai – easily embed ML / AI models in your Dockerfile
To optimize build speed, cache hits, and registry storage, we're building each image reproducibly and indexing the contents with eStargz[0]. The image is stored on Cloudflare R2, and served via a Cloudflare Worker. Everything is open source[1]!
Compared to alternatives like `git lfs clone` or downloading your model at runtime, embedding it with `COPY` produces layers that are cache-stable, with identical hash digests across rebuilds. This means they can be fully cached, even if your base image or source code changes.
And for Docker builders that enable eStargz, copying single files from the image will download only the requested files. eStargz can be enabled in a variety of image builders[2], and we’ve enabled it by default on Depot[3].
Here’s an announcement post with more details: https://depot.dev/blog/depot-ai.
We’d love to hear any feedback you may have!
[0] https://github.com/containerd/stargz-snapshotter/blob/main/docs/estargz.md
[1] https://github.com/depot/depot.ai
[2] https://github.com/containerd/stargz-snapshotter/blob/main/docs/integration.md#image-builders
[3] https://depot.dev
What are some alternatives?
bake-action - GitHub Action to use Buildx Bake as a high-level build command using Depot remote builders
modelfusion - The TypeScript library for building AI applications.
plane - A distributed system for running WebSocket services at scale.
stargz-snapshotter - Fast container image distribution plugin with lazy pulling
trellis - Write Dockerfiles and CI pipelines in TypeScript.
llm.ts - Call any LLM with a single API. Zero dependencies.
obsidian-textgenerator-plugin - Text generator is a handy plugin for Obsidian that helps you generate text content using GPT-3 (OpenAI).
cli - 🖥️ Depot CLI, build your Docker images in the cloud
deep-chat - Fully customizable AI chatbot component for your website