clusterplex
setup-buildx-action
clusterplex | setup-buildx-action | |
---|---|---|
11 | 14 | |
381 | 862 | |
- | 4.8% | |
7.4 | 8.0 | |
3 days ago | 2 days ago | |
JavaScript | TypeScript | |
MIT License | Apache License 2.0 |
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.
clusterplex
-
Run a single Plex server across multiple physical servers?
Clusterplex
-
Plex on Kubernetes with intel iGPU passthrough - Small how to
I'm also very interested in distributing transcoding jobs via https://github.com/pabloromeo/clusterplex. Have you tried that yet?
-
Has anyone used HAproxy for load balancing their PMS?
Here is a link to one of the Cluster projects: https://github.com/pabloromeo/clusterplex
-
[FS][USA-CT] Intel NUC NUC6i7KYK Skull Canyon (32GB RAM, 256GB NVME SSD)
I use a forked version of this: https://github.com/pabloromeo/clusterplex which has been working awesome.
- Unraid, Plex transcoding and Rocket/Alder/Raptor lake or GPU
- Tdarr is a lifechanger!
-
4k transcoding performance, CPU or old Nvidia card?
This is not true. You could setup Plex in a cluster and based on which content is requested let it handle by a certain transcoding worker. You have Clusterplex or you have UnicornTranscoder. Both are actively maintained repositories. This does however require some knowledge of Linux/Kubernetes so if OP (/u/slacktopuss) doesn't know how Ubuntu and Kubernetes works, it's going to take a long time before you're up and running.
-
Transcode Media on different machine
And if UnicornTranscoder isn't it, you can always look intoClusterPlex's implementation. Basically the same as how UnicornTranscoder works (Node.JS as balancer and some remote FFMPEG installs).
-
Multi-arch docker images the easy way, with Github Actions
To see full working examples of this we can take a look at the builds of two pet projects of mine: Docker-Dogecoin and ClusterPlex.
- /r/Plex's Share Your Build Thread - 2021-11-20
setup-buildx-action
-
GitHub Actions Are a Problem
Good luck running this locally. There's no script code to speak of, just references to external "actions" and parameters (for example, https://github.com/docker/setup-buildx-action).
Some CI platforms are just a simple glue layer (Gitlab CI - which I prefer - is one of them), but in most cases Github CI is not. Maybe it adds to the author frustration?
-
Automate Docker Image Builds and Push to Docker Hub Using GitHub Actions š³š
Set up Docker Buildx: We will use the docker/setup-buildx-action action to set up Docker Buildx.
-
One Dockerfile is all it takes, falling in love with bake
Thereās an amazing docker/bake-action which makes it insanely easy to build all of your containers in the most optimal way. Since weāve set the group ādefaultā block in the docker-bake.hcl, config is very minimal. One step in your GitHub Action workflow file will build all of your images and will push all of your cache layers, tag all of your containers, and push all your final images. Youāll still have to do things like checkout the code and donāt forget that youāll want to use the docker/setup-buildx-action since bake is a buildx feature. Thereās one quick gotcha for the actual docker/bake-action. We donāt want to push PR builds and we donāt want to pollute the cache with PR builds.
-
Building with Qemu via Github Actions taking forever. What other options are there?
To be clear, that article does NOT provide a solution for avoiding QEMU. I suggested it because it describes "the hard way" to get a single image multi-arch image. The github action crazy-max/ghaction-docker-buildx has been archived and replaced by docker/setup-qemu-action and docker/setup-buildx-action, which it seems like you were already using.
-
Pushing Cutom Images to Docker Hub using GitHub Actions
Third step is docker/setup-buildx-action configures buildx, which is a Docker CLI plugin that provides enhanced build capabilities.
-
Containerizing Laravel Applications
We then use the docker/setup-buildx-action action to initialize an environment to build Docker images:
-
How to use Docker layer caching in GitHub Actions
The setup-buildx-action configures Docker Buildx to create a builder instance for running the image build. The following step build-push-action, makes use of that instance to build your Docker image. The build-push-action supports all of the features provided by BuildKit out of the box. In our simple example, we are only specifying the Docker context, but more advanced features like SSH, secrets, and build args are supported.
- Why Darwin Failed (2006)
-
Multi-arch docker images the easy way, with Github Actions
# Get the repository's code - name: Checkout uses: actions/checkout@v2 # https://github.com/docker/setup-qemu-action - name: Set up QEMU uses: docker/setup-qemu-action@v1 # https://github.com/docker/setup-buildx-action - name: Set up Docker Buildx id: buildx uses: docker/setup-buildx-action@v1
-
Semantic release to npm and/or ghcr without any tooling
docker/setup-buildx-action@v1 - we use it to setup the docker builder
What are some alternatives?
UnicornTranscoder - Remote transcoder for Plex
setup-qemu-action - GitHub Action to install QEMU static binaries
HBBatchBeast - A free GUI application for HandBrake and FFmpeg/FFprobe with an emphasis on batch conversion (including recursive folder scans and folder watching) -Windows, macOS, Linux & Docker
build-push-action - GitHub Action to build and push Docker images with Buildx
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
intel-device-plugins-for-kubernetes - Collection of Intel device plugins for Kubernetes
metadata-action - GitHub Action to extract metadata (tags, labels) from Git reference and GitHub events for Docker
home-cluster - k3s cluster using gitops (flux) and renovate automation
setup-node - Set up your GitHub Actions workflow with a specific version of node.js
cache - Cache dependencies and build outputs in GitHub Actions