Live data from Hacker News

Serve Your Music Collection Using HTML5, Backbone, and Flask

git.zx2c4.com

11–20 of 86 posts

Re: Serve Your Music Collection Using HTML5, Backbone, and Flask

#11
post #9
post #8

Curious as to why you aren't hosting this on github? I would have loved to star it and then come back later.

your web browser might have a feature similar to the github "star", called a bookmark.

my web browser (and the device I am using changes several times a day - so I must store my bookmarks in cloud). Of course, I could use a cloud bookmark service, or cloned the project to github, but as I said, I was just curious :)

Re: Serve Your Music Collection Using HTML5, Backbone, and Flask

#12
Nice! I'm working on something very similar except I'm using Music Player Daemon as my database. It seemed like I may as well let one of the best do the work rather than deal with syncing the filesystem and mapping ID3 tags in the database on my own.

I'm curious as to the performance of your implementation? Does it handle a large library of music well?

Re: Serve Your Music Collection Using HTML5, Backbone, and Flask

#13

Nice! I'm working on something very similar except I'm using Music Player Daemon as my database. It seemed like I may as well let one of the best do the work rather than deal with syncing the filesystem and mapping ID3 tags in the database on my own. I'm curious as to the performance of your implementation? Does it handle a large library of music well?

MPD is indeed nice, but not the intended use case here. I don't want to be running it on my server or have anything related to audio playback there. They do indeed index metadata, though I'm not sure what their implementation is like. If you finish your project, drop me a line though - would be curious.

ZX2C4 Music handles my 100 gigabyte collection without a hitch, and I'm just using sqlite on my box. If I wanted something more intense, I could run this with PostgreSQL or MySQL or MariaDB or something a little bit better primed for performance (zx2c4 music supports multiple database types out of the box). But, even with sqlite, searches are practically instantaneous.

Re: Serve Your Music Collection Using HTML5, Backbone, and Flask

#17
took a while to get everything up and running -- works nicely now though.

it'd be nice during setup if you used the non-minified includes for all the scripts, with the minified paths commented out (or vice versa!)

i was trying to change the default search terms and they were stuck in scripts.min.js

Re: Serve Your Music Collection Using HTML5, Backbone, and Flask

#18

took a while to get everything up and running -- works nicely now though. it'd be nice during setup if you used the non-minified includes for all the scripts, with the minified paths commented out (or vice versa!) i was trying to change the default search terms and they were stuck in scripts.min.js

Yay! Glad you like it.

As mentioned in the setup guide, you can build unminifed by setting the DEBUG environment variable to 1:

    zmusic-ng $ make clean
    zmusic-ng $ DEBUG=1 make
But, for changing the default search terms, just change the config in frontend/js/app.js _before_ running make. I could add some fancy frontend configuration system, but as there is only that one thing to configure at the moment, this is easy enough.

For more details, all of this is in the README linked above.

Let me know if you have any other questions or feedback. I'm thrilled someone is already making use of the project.

Re: Serve Your Music Collection Using HTML5, Backbone, and Flask

#19
post #18

took a while to get everything up and running -- works nicely now though. it'd be nice during setup if you used the non-minified includes for all the scripts, with the minified paths commented out (or vice versa!) i was trying to change the default search terms and they were stuck in scripts.min.js

Yay! Glad you like it. As mentioned in the setup guide, you can build unminifed by setting the DEBUG environment variable to 1: zmusic-ng $ make clean zmusic-ng $ DEBUG=1 make But, for changing the default search terms, just change the config in frontend/js/app.js _before_ running make. I could add some fancy frontend configuration system, but as there is only that one thing to configure at the moment, this is easy e…

it's pretty neat -- with some nice styling and sort options, there's a lot of potential. but it's a great base. maybe i'll send you a pull request sometime -- edit to say running this on ec2 server with a shared dropbox as the music folder could lead to a whole lot of awesome
Post reply on HN