jgumbley / beatshuffle Goto Github PK

ability for people to contribute via paypal

running this site would cost money.

need to determine an appropriate bitrate and encoding

• minimize bandwidth
• appropriate audio quality

ideally using the LAME encoder

need to automate the conformance of mp3 files using python and / or unix tools

ideally text based adverts.

not displayed in a prominent way in the ideal case.

running this site will cost money

in theory, at extreme scale you'd have several types of server:

• load balancer - brokers various HTTP requests to different server types
• audio server - runs apache httpd with static mp3, js and css content
• webapp server - runs apache httpd, with mod_wsgi and flask application
• database server - runs postgres
• monitoring server - nagios / syslog aggregation monitoring the whole effort

might as well design for this, as it should be little effort.

however, in the first instance one would forget about the load balancer and the monitoring server.

so one server type, which had

• httpd_server
• beatshuffle_static_httpd
• mod_wsgi server
• beatshuffle_flask_app
• postgres_server

also, consider how upgrades would be done.
also, consider how database updates would be done.

is puppet involved, if so how?

http://forge.mysql.com/wiki/TagSchema#Sample_Schema_with_User_Dimension

in order to progressively enhance the visual style of the website you'll need to learn jquery properly, which entails also learning javascript

social interaction drives returning users. therefore there must be some means for people to interact in a forum style (albeit perhaps not in the typical thread based way).

to be expanded upon

need to enhance the shuffle screen to only show the "top" 12 genres. this would be either

• by number of songs - possibly arbitrary
• by number of plays - seems better - although volume required for it to work

also, enhance the tag screens to "group by" other tags exhibited by the members of this tag.

i sense SQL would be the best way to do this.

there are numerous issues, but it is needed.

this would be done via a script, and would modify the apache config, i would expect, this is tied to the provisioner

mp3 streaming is pretty bandwidth intensive. however it is 2011 and bandwidth is pretty cheap.

however in the event of a "slashdotting" would need to be sure there was a provision to "pull the plug" with a stop loss.

this would be a pre-requisite of putting anything on the public internet

if clicked from a non mix associated page, link to general blurb about how seriously copyvio is taken
if clicked from within a mix associated page, then:

• ask if the copyright owner
• if not ask who is asserted as the copyright owner
• if not signed in via twitter ask for email
• mark the song as copyvio_dispute
• email jim