Adding header picture and cleaning up
This commit is contained in:
parent
6f3a81c0f7
commit
c909e3c1fd
5 changed files with 3 additions and 187 deletions
|
@ -1,12 +1,12 @@
|
|||
---
|
||||
layout: post
|
||||
title: Howto - Providing Secure File Storage through Azure API Management
|
||||
subtitle: How to replace your more or less secure ftp server.
|
||||
description: Shared Access Signatures with Azure Storage
|
||||
title: Providing Secure File Storage through Azure API Management
|
||||
subtitle: Shared Access Signatures with Azure Storage
|
||||
category: howto
|
||||
tags: [security, cloud, api]
|
||||
author: Martin Danielsson
|
||||
author_email: martin.danielsson@haufe-lexware.com
|
||||
header-img: "images/bg-post.jpg"
|
||||
---
|
||||
|
||||
Continuing our API journey, we're currently designing an API for one of our most valuable assets: Our content, such as law texts and commentaries. Let's call this project the "Content Hub". The API will eventually consist of different sub-APIs: content search, retrieval and ingestion ("upload"). This blog post will shed some light on how we will support bulk ingestion (uploading) of documents into our content hub using Azure out of the box technology: [Azure Storage SAS - Shared Access Signatures](https://azure.microsoft.com/en-us/documentation/articles/storage-dotnet-shared-access-signature-part-1/).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue