Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Remote media library backend #336

Closed
dz0ny opened this Issue · 10 comments

3 participants

@dz0ny
Collaborator

Goals:

  • Accessible by http protocol.
  • Something like http fronted to http://beets.radbox.org/
  • Support for multiple libraries(friends)
  • Secure(SSL, password,keys protected)

Up-vote with :+1:

@jodal
Owner

There are many different ways this could work. Would you mind to elaborate a bit on what you are thinking? It isn't entirely clear to me from the four bullet points. Thanks!

@dz0ny
Collaborator

@jodal Basic idea is to enable some sort of remote library (that can be accesed over internet or LAN). I'am already using beets to manage my library and as such I am leaning towards beets client for now.

About PR:
Beets also has http api(insecure at the moment), the above PR is simple implementation of beets client. Further down the road, I would like to add more secure implementation(ssl and auth), but that means adding some code to beets web plugin (https://github.com/sampsyo/beets/blob/master/beetsplug/web/__init__.py), but before I do that, there needs to be somewhat usable client.

@kingosticks
Collaborator

Doesn't beats already talk MPD to provide remote access to the music?

@dz0ny
Collaborator

Yep, but it only plays music locally (on system where beets is running). The PR enables (if we go to extremes), to play music with RPI form your friends server. Or to have multiple clients and only one database...

@kingosticks
Collaborator

Yes of course - you'll have to forgive me for being slow there. Personally, if I was doing this I'd be inclined to simply mount the remote directory with sshfs and treat it as a local backend. Or maybe have a stab at #230 which I think would be more widely used (I keep meaning to take a look at this!) and then running a DLNA server alongside the beats server on the remote system(s).

@dz0ny
Collaborator

#230 can only be used in local network.

@kingosticks
Collaborator

True, but then you could use something like himanchi for some security piece of mind. Otherwise you'd be exposing your system and need to be pretty confident with whatever security you implement. Presumably there's also the issue of the legality of the file sharing you're trying to do.

@dz0ny
Collaborator

@kingosticks Plex Media Server does it perfectly legally. On the other side it's illegal to play music in office if you don't pay royalties. But you can bring your own music and play it via headphones :) Also hamachi is little too much, you can use stunnel or ssh proxy. In most offices, IT block those things and HTTP is the only way, sadly.

@kingosticks
Collaborator

Plex Media Server allows access to your own media from remote devices. You mentioned accessing other people's media - I'm no expert on the law or distribution rights etc but maybe just something to keep in mind when discussing the feature. Don't get me wrong though, it's a good solution if the other options don't work for you.

EDIT:
I tell a lie, Plex does in fact advertise the ability to share with others and just says

Be sure you respect the relevant copyright laws when sharing media!

@jodal
Owner

All technology can be misused. It's up to the user, not the technology, to keep within the laws applicable in your jurisdiction. Thus, as long as we don't highlight how to do mischief I don't see a problem in supporting e.g. remote libraries which clearly have lawful uses.

@dz0ny dz0ny closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.