Feature Request: Desktop App

[candideu]

Hi there! Thank you so much for creating this application. I'm wondering if it would be possible to create a desktop app version of this so that users can download the music to their own computers before transferring it to their server.

[jordojordo]

Hello, thanks for your interest!

It's technically possible, and the configuration/features would be slightly different. Just a few questions for clarification:

• Would you be running slskd on your own (locally) or should the desktop app run both slskd and Resonance?
• Do you envision transferring the files over yourself or would that be handled by the app?
• What is your OS?
• Is running the docker container locally not sufficient?

[candideu]

Would you be running slskd on your own (locally) or should the desktop app run both slskd and Resonance?

Ideally, both, if possible.

Do you envision transferring the files over yourself or would that be handled by the app?

I envision doing the transfer myself. My current music library lives on my laptop, and is then synced to my Raspberry Pi (where my navidrome instance lives). I also listen to music files directly on my laptop when I'm offline.

What is your OS?

Windows 10

Is running the docker container locally not sufficient?

I'm running navidrome via a Docker container on my Raspberry Pi, but I'm thinking of ways to make self-hosting music servers easier for people who are less tech-y. Pikapods is one option I'm exploring, and their Navidrome deployment seems to be easier than what I'm currently doing. Users would just need to sync their computer's music folder with the one on the Pikapods server via FTP. That said, users are limited to the apps offered by the platform, so having a desktop version of this app would be ideal to download locally first. I hope I'm making sense (still very new to all of this)

[jordojordo]

This is an interesting idea and could be done from Resonance's perspective for the most part. There are a few pitfalls which would make the setup slightly challenging/cumbersome, particularly around creating API keys and authentication.

Off the top of my head, these are a few of the things someone would need to setup prior to running the desktop app:

• Create a user on the Soulseek net
• Create a user and token on Listenbrainz
  • If using the Last.fm suggestions, create a user and api key there as well
• Generate an api key for slskd

While these things are certainly doable, for the less tech-y people I imagine they would give up pretty quickly considering the amount of configuration necessary beforehand. Unfortunately, the nature of self-hosting things tend to come with lots of applications talking to each other, which can be an authentication nightmare.

It wouldn't be impossible to have Resonance walk the user through this, but that would take a significant effort for development which could take me awhile. I'm not opposed to the idea though and it could be done incrementally.

---

If you want to try something locally for yourself, here's a setup I've been using to test things. It's minimal, but runs slskd and navidrome locally.

Directory structure

├──  config.yaml
├──  data/
├──  docker-compose.yaml
├──  downloads/
├──  navidrome/
│   └──  data/
└──  slskd/
    └──  config/
        └──  slskd.yml

docker-compose.yaml

services:
  resonance:
    image: ghcr.io/jordojordo/resonance:latest
    container_name: resonance
    user: "${UID:-1000}:${GID:-1000}"
    volumes:
      - ./config.yaml:/config/config.yaml:rw
      - ./data:/data
    ports:
      - "8080:8080"
    networks:
      - test-net
    depends_on:
      - slskd
    restart: unless-stopped

  slskd:
    image: slskd/slskd:latest
    container_name: slskd
    user: "1000:1000"
    environment:
      - TZ=America/New_York
    volumes:
      - ./slskd/config:/app:rw
      - ./downloads:/downloads:rw
    ports:
      - "50300:50300"
      - "5030:5030"
    networks:
      - test-net
    restart: unless-stopped

  navidrome:
    image: deluan/navidrome:latest
    container_name: navidrome
    user: "${UID:-1000}:${GID:-1000}"
    volumes:
      - ./navidrome/data:/data
      - ./share:/music/Share:ro
    networks:
      - test-net
    ports:
      - "4533:4533"
    restart: unless-stopped

networks:
  test-net:

config.yaml

listenbrainz:
  username: "your-listenbrainz-username"
  # Generate a token at https://listenbrainz.org/settings/
  token: "your-listenbrainz-token"

slskd:
  host: "http://slskd:5030" # This is pointing to the docker service `slskd`
  # Must match the API key configured in slskd.yml under web.authentication.api_keys
  api_key: "your-slskd-api-key"
  selection:
    mode: manual
    timeout_hours: 24

catalog_discovery:
  enabled: true
  subsonic:
    host: "http://navidrome:4533" # This is the docker service `navidrome`
    # Navidrome admin credentials
    username: "admin"
    password: "your-navidrome-password"
  mode: "manual"

slskd.yml

soulseek:
  # Your Soulseek network credentials (sign up at https://www.slsknet.org/)
  username: your-soulseek-username
  password: your-soulseek-password
  listen_port: 50300

shares:
  directories:
    - /downloads/complete

web:
  port: 5030
  authentication:
    # Credentials for the slskd web UI
    username: your-web-username
    password: your-web-password
    api_keys:
      resonance:
        # Generate a random key, e.g.: openssl rand -hex 32
        # This must match slskd.api_key in config.yaml
        key: your-api-key-here
        role: readwrite

directories:
  downloads: /downloads/complete
  incomplete: /downloads/incomplete