• 8 Posts
  • 79 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle


  • It’s in a really unfortunate state. FOSS wise, the only thing I can recommend is navidrome, BUT finding a good app for it is REALLY hard.

    One step away from that would be plex pass, which is getting enshittified more and more and will likely never reverse course. But if you just want a good self hosted music player, plex pass is much better than navidrome, to the point where you have to be REALLY dedicated to decide on a navidrome solution over plex amp.

    Then there’s Roon, which is as far as you can get from a FOSS solution but is unfortunately the best solution to self hosting and streaming combined, and it has an awesome interface where you can read bios of the artists, select a composition of theirs, view any documented covers or interpretations of it, find out everyone who played on a particular song and what they played, then check out their entire range of output, and so on. There’s unfortunately nothing close to Roon for that experience , but Roon still has MAJOR faults and bugs.

    So you get nothing and you’ll have to make do with that :\

    BTW I’d be stoked to work on a project that aims to make a FOSS version of Roon. I just want to see those fuckers suffer the way I’ve suffered dealing with that horrible program


















  • MonkCanatella@sh.itjust.workstoSelfhosted@lemmy.worldNFS or iSCSI?
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    1 year ago

    That’s a great question. Sounds like iscsi is less flexible but more performant, but potentially only in particular situations you may not encounter in a homelab, while nfs is more flexible and not as performant, depending on what you use.

    From what I’ve learned just reading this thread, you should make iscsi for db and vms, and nfs for stuff like linux isos and other shared media. That said, with iscsi, I believe it’s possible to resize the disk pretty easily. For the DB, you can probably have it be its own little container with an iscsi drive, and expose it over tcp for applications that need access.

    As for your last question about worpress, you could archive it before transfer and either store as an archive or extract it after it reaches its destination. Would be a simple script.