Currently, it is set manually.
Is it possible to create it automatically using the API?
In the production environment, there are 100 space name creations.
enter image description here
Related
I'm very new with Azure and Azure Media Services, so I've a lot of questions about media upload, store and managements. This is the scenario:
I'm creating an API with Asp.Net Core that allow the users to upload Video, Audio and Images. So the user can see the list of videos, images and audio uploaded with a thumbnail. For now I'm just working on Video Uploading. When a video is uploaded, I create a thumbnail that's stored into a Container associate with an Assets ( using a custom TransformOutput ). I'm following the official documentation: https://learn.microsoft.com/it-it/azure/media-services/latest/stream-files-tutorial-with-api .
So, everytime an user upload a video, an Assets and a Container is created. Into container there is the thumbnail and the container is private, so you can not access to the files without an SAS Key. And there is where I've some doubts:
Server side I've to create a List with thumbnails, every thumbnail is stored in a private container with the video file, meta etc etc. but I can't swith the entire container to public because I don't want to allow the direct access to the videos, but just to the thumbnails.
Maybe the best solution is to separate the thumbnails into another Public Container?
My original idea was to create, for every user, 4 Containers:
User_X_VideoContainer ( private )
User_X_AudioContainer ( private )
User_X_ThumbnailsContainer ( public )
User_X_ImagesContainer ( public )
So when an user upload a video, I can store the video into User_X_VideoContainer and Thumbnail into User_X_ThumnailsContainer and use different level of access to the single Container. But I don't know if this is a good practice because Azure Media Services create first an Assets and so a Container with everything inside. So witch is the best way to store and manage user files that had different type of level access?
Thanks!
I would recommend to store the public data in another storage account for better security (and use Azure CDN to cache the content). This storage account could be attached to your AMS account so you can specify this storage account as a destination for the thumbnail output in the job, based on the AMS transform.
Thumbnail output documentation.
I am Customizing the Azure APIM Developer portal. For the Non Production enviornment like Dev, QA etc I am using the same instance of APIM. But the API name is different. I would like to either group them by name so that I see all the API's related to Dev First and rest of the enviornments later. Is there a way i can achieve it? Also we have one template called API List which we can customize. Can we create multiple pages from this template so that I can create different versions of API List for each enviornment?
Your best bet is to use tags. You can assign them to APIs and group by Tags in APIs list. Look for this button next to search field:
if you don't have one, check your customized template, and compare it to default one.
I decided to use back4app for easily creating my backend and for having a built in hosting solution.
I'm quite a newbie with this tool so my question will seem "simple":
I was wondering how will I store the images of my mobile application. As far as I know they use AWS so I thought the service would provide like an interface to upload some images to a S3 bucket...
Should I create a personal bucket or does the service offer that kind of feature ?
The idea is to store then the absolute url of the image in my model. For example each Class has a cover field of type string.
you're right, Back4App use AWS.
Back4App prepared the Backend for you, for example, if you try to save a file direct at your Parse Dashboard, you will can access the image and you already have a absolute URL.You can configure the column with a type File, like below:
Add a column with the File type
After upload a file, you will can access click at the box :)
After that upload the file
I was wondering how to migrate a Virtual Server from one account to another one.
In particular, if I have a VSI on a Softlayer account and I want to migrate the same to a IBM Cloud account (the new one which includes the IaaS part as well), how can I do that?
Thanks in advance guys,
You can "Share Image With Account Number" from the image description page.
You have to make the image template of the VSI and input your account number at first.
After sharing image, you can deploy your VSI from your shared image template.
or you can utilize the function of export and import the image template between your accounts.
I today get Instagram api and add my website live,
I see write:
Client Status: Sandbox Mode GO LIVE
I can't click on ''GO LIVE'' button why ?
You would need to start a submission for approval to go live, though:
Feeds for websites won't be approved; these will remain in sandbox mode and be limited to 500 requests per hour and 20 images. This doesn't sound like much especially for large clients, but if you cache your responses, it's not a problem.
The main confusion is because they have made it sound like every app/feed has to be approved and out of sandbox mode to work, where as the reality is that only fully functioning apps for phones, or a widget plugin really ever need to be.
You will no longer be able to display feeds based on hashtags, only a users own photo's. By getting a client to be a sandbox user, is how you can access their feed without their login information.
Older apps/feeds will need to be updated to use the new code before June or they may stop working.
It's mainly to stop apps hammering instagram's servers for unlimited requests on any hashtag/users they like.
Here is an example of how to fetch and cache images using WordPress's 'set_transient' - you will need to use a loop to output the data.
WordPress Instagram Gist
Here is the relevant piece of information in the dev docs:
Here are some examples of scenarios that will not be approved:
To display content for a personal website. If you are a developer and you want to showcase Instagram content on a website, then you do not need to submit your app for review. By using a client in sandbox mode, you will still be able to access the last 20 media of any sandbox user that grants you permission.
One-off projects. If you are an agency building websites or other integrations, note that we don't grant permissions to clients created for one-off projects. If you are interested in building a product, platform, or widget that will be used as a service across multiple projects, then you may submit a single client_id that you can use across multiple projects.
To use a widget. If you are installing a widget for your website, then you do not need to submit for review. Some widgets may ask you to create a new client id, but you do not need to submit it for review for the widget to work. Your client can remain in sandbox mode and the widget will have access to your last 20 media.
Hope that helps clear some confusion.