https://github.com/mgoltzsche/snapcast-container
Snapcast server and client containers with Spotify Connect (librespot) support
https://github.com/mgoltzsche/snapcast-container
container container-image docker kubernetes librespot snapcast snapcast-docker-image snapcast-server spotify spotify-connect
Last synced: 7 months ago
JSON representation
Snapcast server and client containers with Spotify Connect (librespot) support
- Host: GitHub
- URL: https://github.com/mgoltzsche/snapcast-container
- Owner: mgoltzsche
- Created: 2021-10-03T22:45:52.000Z (almost 5 years ago)
- Default Branch: main
- Last Pushed: 2025-11-13T23:59:10.000Z (9 months ago)
- Last Synced: 2025-11-14T01:15:23.117Z (9 months ago)
- Topics: container, container-image, docker, kubernetes, librespot, snapcast, snapcast-docker-image, snapcast-server, spotify, spotify-connect
- Language: Shell
- Homepage:
- Size: 115 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# snapserver and snapclient containerized
[Snapcast](https://github.com/badaix/snapcast) server and client container images and Kubernetes manifest
## Development
To list the supported targets, run `make help`.
### Prerequisites
* git
* make
* [docker 20+](https://docs.docker.com/engine/install/)
* [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl)
### Build the application
To build the application container image using [skaffold](https://skaffold.dev), run:
```sh
make image
```
### Deploy the application
To deploy the application using [skaffold](https://skaffold.dev), run:
```sh
make deploy
```
To deploy the application in debug mode (debug ports forwarded), stream its logs and redeploy on source code changes automatically, run:
```sh
make debug
```
To undeploy the application, run:
```sh
make undeploy
```
### Apply blueprint updates
To apply blueprint updates to the application codebase, update the [kpt](https://kpt.dev/) package:
1. Before updating the package, make sure you don't have uncommitted changes in order to be able to distinguish package update changes from others.
2. Call `make blueprint-update` or rather [`kpt pkg update`](https://kpt.dev/reference/cli/pkg/update/) and [`kpt fn render`](https://kpt.dev/reference/cli/fn/render/) (applies the configuration within [`setters.yaml`](./setters.yaml) to the manifests and `skaffold.yaml`).
3. Before committing the changes, review them carefully and make manual changes if necessary.
TL;DR: [Variant Constructor Pattern](https://kpt.dev/guides/variant-constructor-pattern)
## Release
The release process is driven by [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0-beta.4/), letting the CI pipeline generate a version and publish a release depending on the [commit messages](https://semantic-release.gitbook.io/semantic-release/#commit-message-format) on the `main` branch.