- Blob storage vs file storage how to#
- Blob storage vs file storage code#
azure-popup: Navigate to azure -popup/build/index.html, upload this file as an asset in your stack by referring to the Create/Upload Assets guide. Blob storage vs file storage code#
We will upload the code in this file in the extension source code field of our extension in the next step.
azure: Navigate to azure /build/index.html file. The support team will provide you with the source code that contains the following files: If Extensions are part of your plan, contact our Support team to get the code for the extension. To set up an extension in Contentstack, log in to your Contentstack account and follow the steps given: Add the Azure Blob Storage Custom Field Extension to your Stack. Blob storage vs file storage how to#
If it isn't, then generate a new token.Īdditional Resource: Learn in detail how to create SAS token in Azure Storage Explorer. Note: The SAS token (URL) should be in the following format starting with a “?” sign.
Note down the token, we will use it to set up our extension.
You will find the SAS token of your container. Once done, click on the Generate SAS and connection string button. Now specify your access policies, token lifespan, time zone and define your container’s permission as shown below:. Click on your Blob Container, in the left navigation, scroll down and under the Security + networking section select the Shared access signature option. Navigate to the Storage accounts page and expand your Blob Container. To get the SAS token, follow the steps given below: This token will help you set up your extension. Now lets create and retrieve SAS token from your Azure Storage account. Refer this detailed guide on how to enable CORS in Azure. Note: It is mandatory to enable CORS for your extension to work smoothly. Finally, enable Cross-origin resource sharing ( CORS) in your Storage account. Click on the Public access level dropdown and select the Blob(anonymous read access for blobs only) option. Select the container(s) you created and click on the Change access level button. To access the data of a container, you need to make the containers public. You can add more than one container in your account. 
Once that is done, click on the container you created and add content to the container by clicking on the Upload button. Now, click on + Container button and follow the onscreen instructions to create your container. To do that, select Containers from your left menu portal within the Storage accounts page. To start using your Storage, you need to create Containers for your account that will hold your data. Select your account type (you need a Basic storage account for this guide) and proceed to create your Azure storage account. Navigate to the Storage accounts page and click on Create. Select Storage accounts from the left menu of your Azure portal. Log into your newly created account and proceed to create your Azure storage account. Follow the on-screen instructions and create your Azure account.Īdditional Resource: For more information about the features of Azure Blob Storage, its pricing, and FAQs, visit the Azure Storage page. If you already have an account, just log in with your credentials. On the next screen, you'll be asked to log in. To do that, follow the steps given below: In order to use this extension, you need to create an account with Amazon Web Service. Add the Azure Custom Field Extension to your Stack. Retrieve SAS Token from Azure Storage Account. Create an Azure Blob Storage Service Account. Microsoft Azure Account and Azure Storage Account enabled. This step-by-step guide explains how to create Azure Blob Storage custom field extension for your content types in Contentstack. Thus, while creating entries, you can select any data (as mentioned above) as the input value for the field in the content type of your stack. Azure Blob Storage custom field extension allows you to fetch your data (documents, images, videos, etc) from your Azure Blob Storage account and display them into a field of a content type in your stack.
0 kommentar(er)
