Undeleting profile
Using Jamroom
I thought profile admin lets that user admin ALL profiles. That's not what we want.
Forum Activity for @dannya
Undeleting profile
Using Jamroom
I did notice that when I look at list of accounts in the user account data browser, the label account does not show a profile associated with it. So I think don't think the link is working. Or at the very least, the account can't figure out which profile is the primary account.
There are 3 profiles linked to the account: 2 artist profiles (in artist quota) and 1 newly created label profile (in lable quota).
Additinally, now, when I log in as label acocunt, I can't even edit settings of my artists profiles.
Undeleting profile
Using Jamroom
Confirmed. is in the correct Label profile.
updated by @dannya: 01/14/15 12:38:18AM
Undeleting profile
Using Jamroom
I was able to re-create a new profile from tools and linked it to the account, and the artist profiles were actually already linked to it. I also made sure it used the label quota. However, it doesn't seem to be recognizing it as a label profile.
-When I log in, it does not take me to my default label profile
-The profile menu is not visible
-If i type in the label profile url, i can get there, but the menu does not give me the abiltiy to switch profiles
- If i go to profile settings, it says "You do not have the proper privileges to perform that action!"
So, even though I created the proper profile and linked it to the account when I did, something is wrong.
Undeleting profile
Using Jamroom
Is there any way to undelete a profile?
I have a label (power user) that accidently deleted their label profile. Their profile menu does not appear now and their is no "main" profile associated with the account. They can no longer create new profiles either because the "create profile " button was on their profile page.
Can I undo the deletion somehow? Or how can I create a new profile for them and re- associate the old linked profiles and content?
updated by @dannya: 02/20/15 02:50:10PM
Jamroom and proxima
Proxima
I know there's no documentation yet, but is it safe to run proxima on an existing jamroom build? there is no conflict with any existing modules right?
I wanted to be sure because it the install only mentioned to in stall Proxima on the JR core. It didn't mention one way or another any other modules being installed.
updated by @dannya: 02/09/15 04:26:30AM
s3 and conversion server
Jamroom Developers
Yes, that helps a bit. At least developers have a place to start. I will point them to this thread if there are additional questions. If there is any way to do this as a module that can be used by others, I'd be happy to post the resultant code.
I appreciate you trying to get a framework in place sooner, but unless you can have something next week, I can't wait on this any longer. I have a feeling you already have a full plate with pending cloud beta and documentation, and the proxima generic api module and documentation, new jamroom site, and supporting the current release.
If anything, I may ask if you can take a look at the final code to make sure we haven't done anything that might cause problems for future releases or other modules.
Thanks again. Keep you posted.
updated by @dannya: 01/08/15 05:29:14PM
s3 and conversion server
Jamroom Developers
I realize that. Many platforms that start off as a monolith application. The idea is to start breaking out the modules that need to scale into microservices with their own api's and let them scale independently. The conversion server is a good example of that (in principle; yet to see if it scales the way I want). (Soundcloud did a great engineering post on their migration https://developers.soundcloud.com/blog/building-products-at-soundcloud-part-1-dealing-with-the-monolith
This is also why I'm interested in the Proxima stuff. I've worked for some companies with massively scaled apps, and we always build the API FIRST and built the application on top of that. For everything I wanted to do, I thought I would be able to do it much faster with JR. The framework for the quotas, profiles, and user management was exactly what I was looking for. Delivery could be scaled pretty easily with caching and cdn's. But media processing and storage do not. That's why I've been pushing hard for those to be released. The only other thing is storage. I understand your need to dis intermediate the sevice provider, but that's obviously much more difficult than what I am trying to do.
We've already rewirtten a number of modules or created our own to suit our needs: all the commerce functionality, players, sharing, extensive changes to jr audio, etc.
I have no doubt the developers will be able to do make the change to s3. I'm a little concerned about compatibility with future releases and modules because its a function that almost everything else relies on. If the core media storage function are just in those 2 files, it might not be too bad though. Otherwise, I may just need to just start a new branch and rely only on our own development going forward.
updated by @dannya: 01/08/15 02:19:54PM
s3 and conversion server
Jamroom Developers
This is a huge problem form me that I've been asking about for a long time. Having to use EBS (or storage at a regular hosting provider) basically triples my storage costs and breaks by business model. As I mentioned before, as a cloud application, storage and bandwidth are my biggest costs.
I don't know know how many other customers you have for your cloud services, so I don't know how much demand you are expecting. But I have a feeling I'm one of your first and have been asking about this stuff a long time. Almost all major media cloud applications and media platforms rely on one of the top 3 cloud storage platforms. Local storage does not scale economically for cloud applications
After over a year in development, I feel like I'm pretty screwed right now. I don't think I can launch on ebs and migrate thousands of files and 100's of TBs of content once I'm in production.
I am happy to have my developers do the work, but I need to provide some guidance. From what it sounds like, we have to go in and find every instance where media read/written and use the api to reference an s3 object instead. For just the media files, this CAN'T be that extensive.
Ingest process
Conversion/info extraction
Player requests
Download requests
Image uploads and requests.
I feel this could be done in a couple of weeks if we new what to look for.
