build-push-action
plane
build-push-action | plane | |
---|---|---|
3 | 23 | |
20 | 1,583 | |
- | 2.3% | |
6.8 | 9.4 | |
about 1 month ago | 5 days ago | |
TypeScript | Rust | |
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:
plane
- Plane: A distributed system for running WebSocket services at scale
-
Pingora: HTTP Server and Proxy Library, in Rust, by Cloudflare, Released
One reason I'm excited about this is that it appears to let you write arbitrary routing logic into a layer 7 proxy. This is something we had to build for https://plane.dev and it would have been nicer to use something like this, but we couldn't find anything like it at the time.
- Plane: A distributed system for running stateful WebSocket services at scale
-
"VMWare rewritten in Rust
Of course, as a user, I would prefer as much as possible to be under MIT or Apache. See for instance https://plane.dev/ for a similar project which is MIT licensed and https://jamsocket.com/ for the commercial version.
- Session back end orchestrator for ambitious browser-based apps
- Plane – open-source Jira alternative
- Plane: A container orchestrator for ambitious browser-based applications
-
The growing pains of database architecture
From an earlier blog post[1], the system for synchronizing file/document state lives independently for their database. As I understand it, their database is for metadata rather than actual document content.
> It’s worth noting that we only use multiplayer for syncing changes to Figma documents. We also sync changes to a lot of other data (comments, users, teams, projects, etc.) but that is stored in Postgres, not our multiplayer system, and is synced with clients using a completely separate system that won’t be discussed in this article. Although these two systems are similar, they have separate implementations because of different tradeoffs around certain properties such as performance, offline availability, and security.
This post[2] goes into more detail on how they spin up backend processes to serve as the source of truth while documents are open (we took heavy inspiration from it when building https://plane.dev, which aims to be an open-source implementation of that architecture.)
[1] https://www.figma.com/blog/how-figmas-multiplayer-technology...
-
Show HN: Accelerated Docker builds on your local machine with Depot (YC W23)
We have been happily using Depot for months now to build https://plane.dev. Prior to finding Depot, we basically gave up on building an M1 image from a GitHub action.
(btw, I always get suspicious when a Show HN post has a lot of praise in the comments, but I swear the Depot folks did not ask me to post anything and I only saw the post because I was checking HN)
-
Launch HN: Depot (YC W23) – Fast Docker Images in the Cloud
Congrats on the launch!
We've been using Depot with Plane (https://plane.dev/). Prior to depot, I had to disable arm64 builds because they slowed the build down so much (30m+) on GitHub's machines. With Depot, we get arm64 and amd64 images in ~2m.
What are some alternatives?
bake-action - GitHub Action to use Buildx Bake as a high-level build command using Depot remote builders
Centrifugo - Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.
depot.ai - Embed machine learning models in your Dockerfile
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
trellis - Write Dockerfiles and CI pipelines in TypeScript.
pingora - A library for building fast, reliable and evolvable network services.
aper - A Rust data structure library built on state machines.
nix2container - An archive-less dockerTools.buildImage implementation
cli - 🖥️ Depot CLI, build your Docker images in the cloud
statebox_riak - Convenience library that makes it easier to use statebox with riak, extracted from best practices in our production code at Mochi Media.
XQuartz - An X11 server and client libraries for macOS
pigeon - Diff, patch, merge, and synchronize JSON documents with an Automerge-compatible interface