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

Hey all good by me. Different setups for different folk!

I use a combination of a custom built Caddy Docker container, Technitium for DNS, and DNSWeaver.

Automated DNS Entries, Automated Reverse Proxy entries all with Docker labels.

The reverse proxy is infernal. I type sub.domain.tld to get to my internal site. All with automated certs.

Makes it so I dont have to remember IP and port combos

Feishin on Desktop. Symfonium on phone. (I can also recommend Tempo, which is open source but doesn’t work over Android Auto last I tried.) To host my music I use Navidrome. Which I have setup as a docker container, behind a reverse proxy. The files are stored on my NAS. To access remotely I have Wireguard setup. That being said, to use Android Auto with Symfonium while my Navidrome is only accessible on my network or over VPN I use split tunneling otherwise Android Auto throws a fit.

I would hope so. That and the extensions.

For my homelab:

Mullvad: ~$6/month Domain: $8/year

And whatever cost for electricity for running a singular mini PC, Pi4, and my synology.

Cost isn’t much.

I currently pay for Bitwarden and self host Vaultwarden. As long as we can still use the Bitwarden app with Vaultwarden, I won’t have a problem.

There isn’t another password solution I want to use currently.

If we lose that self-hosted feature for Vaultwarden I will jump ship to a keepass compliant solution.

I’ll optimistically sit back and see what comes of this. I’m happy with vaultwarden.