Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull new content to feature branch #285

Merged
merged 2 commits into from
May 20, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
5 changes: 5 additions & 0 deletions get-started/azure-migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,11 @@ Planning to migrate api.video from Azure Media Services? We got you covered!

You can import all of your video content, both from Azure's Blob storage and Media storage using api.video's Import tool.

{% capture content %}
When you import videos from Azure Media Services, you have the option to enable importing video captions in `VTT` format. The imported captions will be automatically linked to the videos they belong to. Videos with multiple captions are also handled by the Import tool.
{% endcapture %}
{% include "_partials/callout.html" kind: "info", content: content %}

## What's the cost?

We understand that when you want to move to a different provider, it takes effort and development resources. You also want to make sure that it is cost-efficient, especially if you are moving to api.video to save costs.
Expand Down
42 changes: 42 additions & 0 deletions get-started/cloudinary-migration.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
title: "Cloudinary migration guide"
slug: "cloudinary-migration"
meta:
description: This page gets users started on how to migrate from Cloudinary to api.video.
---

# Cloudinary migration guide

Planning to migrate api.video from Cloudinary? We got you covered!

Using the api.video Import tool, it only takes a couple of clicks to migrate all of your video content from Cloudinary to api.video. The tool only requires your cloud name, API key, and API secret from Cloudinary.

Check out the [Import tool](https://dashboard.api.video/import) to get started.

## What's the cost?

We understand that when you want to move to a different provider, it takes effort and development resources. You also want to make sure that it is cost-efficient, especially if you are moving to api.video to save costs.

api.video gives you the ability to **migrate for free** and avoid paying anything for encoding!

## Collect Cloudinary credentials

To access your credentials on Cloudinary, simply visit your Dasboard. You will immediately see all credentials you need to start the import process under Product Environment Credentials:

![Collecting credentials on Cloudinary](/_assets/get-started/migration-guide/cloudinary-1.png)

## Import your videos

Once you have all the credentials, you can start the migration.

1. Navigate to the api.video [Import tool](https://dashboard.api.video/import).

2. Select **Cloudinary** from the list.

3. Next, click on Sign in to Cloudinary and paste in the Cloudinary credentials that you collected.

4. Next, the tool retrieves the available videos from Cloudinary.

5. Select the videos you want to import, and start the process.

The process displays the upload status and encoding status for each video.
8 changes: 8 additions & 0 deletions get-started/migration-guides.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,8 @@ Moving to a different provider takes time, effort, and development resources. ap

{% include "_partials/hagrid-item.md" title: "Wistia", image: "/_assets/get-started/migration-guide/wistia.png", subtitle: "", link: "./wistia-migration.md" %}

{% include "_partials/hagrid-item.md" title: "Cloudinary", image: "/_assets/get-started/migration-guide/cloudinary-logo.png", subtitle: "", link: "./cloudinary-migration.md" %}

</div>

## FAQs
Expand All @@ -42,4 +44,10 @@ Technically speaking no. When you migrate your assets, api.video generates new u
<summary><b>Will api.video help me create a mapping from old assets to new assets?</b></summary>
<p>
Yes! The Import tool automatically creates a mapping in <code>csv</code> and in <code>JSON</code> formats.
</details>

<details>
<summary><b>Can I import video captions with the Import tool?</b></summary>
<p>
Yes! However, note these limitations: importing captions is currently only supported from <a href="/get-started/azure-migration">Azure Media Services</a>, and only in <code>VTT</code> format.
</details>
2 changes: 2 additions & 0 deletions navigation.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -22,5 +22,7 @@
href: /get-started/vimeo-migration.md
- label: Wistia
href: /get-started/wistia-migration.md
- label: Cloudinary
href: /get-started/cloudinary-migration.md
- label: SDK Catalog
href: /sdks/README.md
Loading