s3 and conversion server
Jamroom Developers
To be honest with you, I'm not sure how Jamroom is going to perform with 100's of Terabytes of data - that's many, many, many times higher than 99.9% of Jamroom users are going to be using. The reason I say that is I want you to be aware that we do NOT develop or test Jamroom to run at Twitter like scale, as that is way beyond the needs of our customers. There's nothing in Jamroom to prevent it from working that large, but I need you to know that our time and energy is not going to be invested into optimizations for that large (where you really are going to need A LOT of custom solution and a dedicated DevOps staff).
We definitely do plan on having cloud storage support, but it's going to take more time before it is ready mainly because:
- it's not our highest priority - I personally like working on it and try to make time to do it, but we have a lot more work that impacts a much larger amount of customers that will be prioritized first.
- I don't want to develop a layer that is JUST for S3. As soon as we do we're going to have someone asking for CloudFiles support, or GAE, or Heroku, or whatever is popular a year or two from now. So it has to go in as a full "replacement" for the file system, which is more extensive than just dealing with what you're looking for.
So for now I would recommend having your developers become familiar with the functions in jrCore/lib/media.php - that's where the bulk of the media functions are and would need to be updated to work directly with S3.
You also will want to check out the jrAudio/include.php for functions related to audio handling.
Hope this helps!