

Yeah, I manually copied the link to the full package. As well as manually reinstalled


Yeah, I manually copied the link to the full package. As well as manually reinstalled


Thats where I got mine, GitHub, ubdating with Obtainium!


Good to know! Thanks for sharing. Tempus seems quite nice. Though Android Auto didnt work for me last I checked even with the update.


I personally use Navidrome to host the music, and there are multiple android clients; personally I use Symfonium, but there is also Tempus and Tempo.
Jellyfin can also do Music.
The Music I put on Navidrome already has correct metadata, so I haven’t worried about that aspect.
Its easy to maintain because I run it with docker.





Looking forward to trying this out. Been using Symfonium for its android auto support. Glad to see another Navidrome supporting client with android auto capabilities.


I have a Dockerifle:
ARG CADDY_VERSION=2.11.3
FROM caddy:${CADDY_VERSION}-builder-alpine AS builder
RUN xcaddy build \
--with github.com/caddy-dns/cloudflare
FROM caddy:${CADDY_VERSION}-alpine
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
and the docker-compose.yml file I have this snippet at the top, of course this isn’t the full file as there are specifics to my usecase in my full yml:
services:
caddy:
pull_policy: build
build:
context: .
And to build new versions I modify the Dockerfile after doing a docker compose down, and then to build the new version I use docker compose up.``
Though this is outdated for my current setup, as I also use github.com/lucaslorentz/caddy-docker-proxy by adding “–with github.com/lucaslorentz/caddy-docker-proxy/v2” below where I added the Cloudflare repo.
This is so I can use Docker Labels to to automate entries.


I have a Dockerifle like that:
ARG CADDY_VERSION=2.11.3
FROM caddy:${CADDY_VERSION}-builder-alpine AS builder
RUN xcaddy build \
--with github.com/caddy-dns/cloudflare
FROM caddy:${CADDY_VERSION}-alpine
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
and the docker-compose.yml file I use:
services:
caddy:
pull_policy: build
build:
context: .
And to build new versions I modify the Dockerfile after doing a docker compose down, and then to build the new version I use docker compose up.


I currently build my own Caddy docker container with a Dockerfile using xcaddy and the caddy-builder-alpine image.
xcaddy adds these github.com/caddy-dns/cloudflare github.com/lucaslorentz/caddy-docker-proxy/v2
What started off as a kid as mild interest in something “different.” Different in the sense that it was different than that of what I grew up using. Anywhere from the lame old school Mac computers in primary school, to the Windows PCs that were everywhere. I did go to school for a degree in Cyber Security; and of course got my hands on some different Linux distros over the years, so between my younger years of tinkering, and schooling I had exposure to Linux early on.
Fast forward a bit, years and years pass by and I was a Windows user because that was just readily available and accessible and what I had primarily used for most of my life; and I was getting fed up with what Microsoft was doing and pushing. That being said, I initially switched from Windows 10/11 to Arch Linux out of hatred for Microsoft.
Well, my reasoning has changed drastically. It used to be because I hated Microsoft and all of their shenanigans. Now I use Linux out of love for Linux. Sure, I still hate Microsoft; but that is a naturally progression the further I get into my niche.
I love open source, and my beliefs on open source has permeated through other beliefs. I think that the collective of human knowledge should be effectively “open source” and available to all. We shouldn’t be limited on what we want to learn just because of a corporation or business entity says they arbitrarily own a subset of knowledge.
Anyways, tldr; started as hate for Microsoft, and turned into genuine love for Linux and Open Source Software.