Selfhosted

60526 readers

936 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

483

Mixarr – a music discovery companion for Lidarr/Plex (lemmy.world)

submitted 6 months ago* (last edited 4 months ago) by aquantumofdonuts@lemmy.world to c/selfhosted@lemmy.world

75 comments fedilink hide all child comments

Hey everyone,

I'm new here! I wanted to share a music search and discovery tool for Lidarr. It plugs into Spotify, TIDAL, Deezer, Last.fm, MusicBrainz, Plex/Tautulli, Jellyfin, and even some AI recommendations.

GitHub: https://github.com/aquantumofdonuts/mixarr

Website: https://aquantumofdonuts.github.io/mixarr/

What it does:

Connects to Lidarr and analyzes your existing artists
Hooks into Spotify, TIDAL, Deezer, Last.fm, MusicBrainz, Plex/Tautulli, and AI services
Finds related/similar artists, new releases, charts, labels, playlists, etc.
Gives you a review queue to approve or dismiss discovered artists
Automatically adds approved artists to Lidarr with the profile you choose
Has a universal search and discovery interface across all services
Runs as a web app (Next.js frontend + Express backend) and plays nice with Docker

Why I built it:

I wanted one tool that I could point at my Lidarr library and get a steady stream of relevant artist recommendations.

Basically, make music discovery feel as automated and “infrastructure-y” as the rest of the *arr ecosystem.

Current status:

Working with Lidarr + Spotify/TIDAL/Deezer/Last.fm/MusicBrainz + Plex/Tautulli
Has subscriptions for different discovery sources (charts, playlists, related & followed artists, etc.)
Docker-compose setup available, plus local dev if you prefer
Early but usable; I’m actively using it myself and iterating

If you try it, I’d love to hear any feedback! Thanks!

EDIT: version 2.0 released today February 10, 2026, with some nice updates

you are viewing a single comment's thread
view the rest of the comments

[–] Statick@lemmy.world 2 points 6 months ago* (last edited 6 months ago) (1 children)

First, thank you for making this. Seems very useful.. That being said I'm having the same issue, even after mapping port 80, it redirects to https/443 no matter what I do.

services:
  mixarr:
      container_name: mixarr
      image: ghcr.io/aquantumofdonuts/mixarr:v1.1.0
      ports:
        - 3010:80 # Edit: change 80 to 3000 in order to bypass caddy in the container
        - 3443:443
      volumes:
        - ~/mixarr-data:/data
      environment:
        - SESSION_SECRET=$(openssl rand -hex 32)
        - FRONTEND_URL=https://my-domain:3443/
        - BASE_URL=http://my-domain:3010/
      restart: unless-stopped

Edit: Just realized you have it using caddy, always, and it is set to redirect to 443. You should give people the option to run without caddy in the container. I have my own instance of caddy running, I don't need it built in.

That being said, changing it from pointing to port 80 and instead to port 3000 allows me to access it over http but ends up having authenticaton issues when trying to change settings.

Edit 2: Oh there is a much more robust docker-compose file. I was just going based on the readme. Will give it a try a bit later.

[–] NarrativeBear@lemmy.world 2 points 5 months ago* (last edited 5 months ago)

Thank you, your comment here helped me sort my issue out.

For anyone if you want to access this without the built-in proxy/caddy server set your ports in your docker compose like so.

3010:3000
3443:443 (this is the caddy port inside the container)