slskd
build-push-action
slskd | build-push-action | |
---|---|---|
46 | 31 | |
755 | 4,003 | |
5.7% | 2.1% | |
9.4 | 8.5 | |
5 days ago | 11 days ago | |
C# | TypeScript | |
GNU Affero General Public License v3.0 | 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.
slskd
-
Automation
If you're looking for an API, there's slskd which runs as a daemon and offers a REST API for searching and downloading.
-
can you sync up seeker and soulseek?
There's even an example daemon that can give remote access, so you wouldn't even have to have Soulseek and Seeker on the same computer: https://github.com/slskd/slskd
-
Soulseek CLI Client for Linux Server?
Itβs not cli, but you could try slskd in a container - it has a nice web interface.
- Available clients?
- Is there a 32bit version of Soulseek for Linux?
-
soulseek on cloud-based virtual desktop?
Another option along similar lines: https://github.com/slskd/slskd
-
Help configuring slskd on Linux
Hi, I just stumbled upon slskd (https://github.com/slskd/slskd), and I'm struggling to configure it. I've downloaded the binary and executed it with command line and it created a config file. It keeps saying the login and password are wrong no matter what i put there. Also I have no idea how it can open the web UI. I think I'mm missing many things. I appreciate the help.
-
Using Soulseek / Nicotine+ on a Synology NAS in Docker
I had a similar problem: I wanted to run a Soulseek client on my home server / NAS. I eventually opted for https://github.com/slskd/slskd which provides a web interface, even though Nicotine+ is superior. Let's hope either slskd improves or Nicotine+ gets a remote control option (it can already run headlessly, so I guess develop is in progress).
-
Slskd - anyone running it?
Saw a post over on /r/DataHoarder regarding SLSKD. Hadn't heard of it before. Anyone vouch for it?
-
After over 15 years of ripping and downloading, my music library just reached 20TB. AMA
And, if you prefer a self hosted web app, you'll like slskd.
build-push-action
-
Continuous Deployment with GitHub Actions and Kamal
We use the docker/build-push-action to build the application image. In addition to setting the correct tag, the image build step must also provide a label matching your service name. Because the image should be pushed to your container registry, we set push: true, and because we want ludicrous build speed we instruct the build step to utilize the GitHub Actions cache.
-
Dockerize and Deploy a NodeJS Application to Cloud Run with GitHub Actions
name: Lint and Dockerize the app on: push: branches: [master] pull_request: branches: [master] env: # Use docker.io for Docker Hub if empty REGISTRY: docker.io # github.repository as / IMAGE_NAME: ${{ github.repository }} jobs: build: runs-on: ubuntu-latest permissions: contents: read packages: write steps: - name: Checkout repository uses: actions/checkout@v2 - name: Set up Google Cloud uses: google-github-actions/[email protected] with: project_id: ${{ secrets.GCP_PROJECT_ID }} service_account_key: ${{ secrets.GCP_SA_KEY }} # Login against a Docker registry except on PR # https://github.com/docker/login-action - name: Log into registry ${{ env.REGISTRY }} # if: github.event_name != 'pull_request' uses: docker/login-action@v1 with: username: ${{ secrets.DOCKER_USERNAME }} password: ${{ secrets.DOCKER_PASSWORD }} # Extract metadata (tags, labels) for Docker # https://github.com/docker/metadata-action #- name: Extract Docker metadata # id: meta # uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38 # with: # images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} # Build and push Docker image with Buildx (don't push on PR) # https://github.com/docker/build-push-action - name: Build and push Docker image uses: docker/build-push-action@v2 with: context: ./ tags: ${{ secrets.DOCKER_USERNAME }}/magga:latest push: true file: ./Dockerfile - name: Image digest run: echo
-
Automating Tag Creation, Release, and Docker Image Publishing with GitHub Actions
docker/build-push-action@v4 to build and push Docker images with Buildx.
-
How to use notification in gitea actions
Hmmm interesting question... I use the following in my yaml: yaml - name: Build and push uses: https://github.com/docker/build-push-action@v2 can't you just use like: yaml - name: NTFY uses: https://github.com/dawidd6/action-send-mail@v3 and use the actions explained in the links?
-
Where do you commit files for containers that run CI scripts?
Docker made some decent actions free to use like this one to build and push docker images to registries.
- [Darksouls] Remaster pour PC Controller ne fonctionne pas ?
-
Automate Docker Image Builds and Push to GitHub Registry Using GitHub Actions π
name: Docker Image Publish on: push: branches: [ "main" ] # Publish semver tags as releases. tags: [ 'v*.*.*' ] pull_request: branches: [ "main" ] env: # Use docker.io for Docker Hub if empty REGISTRY: ghcr.io # github.repository as / IMAGE_NAME: ${{ github.repository }} jobs: build: runs-on: ubuntu-latest permissions: contents: read packages: write # This is used to complete the identity challenge # with sigstore/fulcio when running outside of PRs. id-token: write steps: - name: Checkout repository uses: actions/checkout@v3 # Install the cosign tool except on PR # https://github.com/sigstore/cosign-installer - name: Install cosign if: github.event_name != 'pull_request' uses: sigstore/cosign-installer@f3c664df7af409cb4873aa5068053ba9d61a57b6 #v2.6.0 with: cosign-release: 'v1.11.0' # Workaround: https://github.com/docker/build-push-action/issues/461 - name: Setup Docker buildx uses: docker/setup-buildx-action@v2 # Login against a Docker registry except on PR # https://github.com/docker/login-action - name: Log into registry ${{ env.REGISTRY }} if: github.event_name != 'pull_request' uses: docker/login-action@28218f9b04b4f3f62068d7b6ce6ca5b26e35336c with: registry: ${{ env.REGISTRY }} username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} # Extract metadata (tags, labels) for Docker # https://github.com/docker/metadata-action - name: Extract Docker metadata id: meta uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38 with: images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} # Build and push Docker image with Buildx (don't push on PR) # https://github.com/docker/build-push-action - name: Build and push Docker image id: build-and-push uses: docker/build-push-action@v4 with: context: "{{defaultContext}}:src" push: ${{ github.event_name != 'pull_request' }} # Don't push on PR tags: ${{ steps.meta.outputs.tags }} labels: ${{ steps.meta.outputs.labels }} cache-from: type=gha cache-to: type=gha,mode=max
-
Automate Docker Image Builds and Push to Docker Hub Using GitHub Actions π³π
Build and push Docker image: We will use the docker/build-push-action action to build and push the Docker image to Docker Hub. We will use the following inputs:
-
Show HN: Cross-Platform GitHub Action
I previously tried to use Docker `docker/setup-qemu-action@v2` and `docker/setup-buildx-action@v2` for this purpose (see that example https://github.com/docker/build-push-action#git-context). Thanks to buildkit, platform switching works transparently. However, building on ARM via QEMU on GitHub Actions is terribly slow (something like 5 times more), which is hard to accept. Therefore, full of hope, I am waiting for GitHub Actions to make cloud runners available on ARM, because it is a blocker for the implementation of Graviton on the AWS environment for us.
For a while, the blocker in GitHub Actions for providing ARM support was that Azure doesn't have ARM support. In this way, the Azure cloud offering may determine the habits of AWS consumers.
-
Do I need Dockerhub for CI/CD with Github Actions?
Build and push an image in CI. This extends #2 by pushing the image to a container registry. DockerHub is the default registry in Docker, but isn't the only registry. You could use GitHub's Container Registry as well. We (Docker) have supported GitHub Actions with lots of documentation to help out. You could then extend the pipeline to actually deploy your updated image too.
What are some alternatives?
soulseek-docker - π³ Soulseek Docker Container
setup-buildx-action - GitHub Action to set up Docker Buildx
Lidarr - Looks and smells like Sonarr but made for music.
ssh-action - GitHub Actions for executing remote ssh commands.
nicotine-plus - Graphical client for the Soulseek peer-to-peer network
metadata-action - GitHub Action to extract metadata (tags, labels) from Git reference and GitHub events for Docker
soulseek - soulseek vnc service
nocodb - π₯ π₯ π₯ Open Source Airtable Alternative
PowerToys - Windows system utilities to maximize productivity
ghaction-docker-meta - GitHub Action to extract metadata (tags, labels) for Docker [Moved to: https://github.com/docker/metadata-action]
Soulseek.NET - A .NET Standard client library for the Soulseek network.
upload-artifact