History

Karl Horky 3ad55721d1 Remove incorrect entries for pnpm debug log (#47241 ) Reasons for making this change: - it is contained within `node_modules/`, which is already ignored - the previous versions, which were not in `node_modules/`, did not have a period at the beginning of the filename Links to documentation supporting these rule changes: Changelog with proof here: `ba4b2db1f2/pnpm/CHANGELOG.md (L3330)` History: - my PR to remove this from `github/gitignore` here: https://github.com/github/gitignore/pull/4250 - First introduced in `github/gitignore` in https://github.com/github/gitignore/pull/3732 by `@sakurayang` (merged by `@martinwoodward`) <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation or adding/fixing Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>		2023-03-26 22:26:05 -07:00
..
components	Example/with apivideo (#45272 )	2023-02-02 13:44:37 +00:00
pages	Example/with apivideo (#45272 )	2023-02-02 13:44:37 +00:00
public	chore(examples): update with-apivideo (#39727 )	2022-10-20 17:05:54 +02:00
style	chore(examples): update with-apivideo (#39727 )	2022-10-20 17:05:54 +02:00
.env.local.example	chore(examples): update with-apivideo (#39727 )	2022-10-20 17:05:54 +02:00
.gitignore	Remove incorrect entries for pnpm debug log (#47241 )	2023-03-26 22:26:05 -07:00
next-env.d.ts	Remove incorrect entries for pnpm debug log (#47241 )	2023-03-26 22:26:05 -07:00
next.config.js	Example/with apivideo (#45272 )	2023-02-02 13:44:37 +00:00
package.json	Example/with apivideo (#45272 )	2023-02-02 13:44:37 +00:00
README.md	Example/with apivideo (#45272 )	2023-02-02 13:44:37 +00:00
tsconfig.json	chore(examples): update with-apivideo (#39727 )	2022-10-20 17:05:54 +02:00

README.md

api.video video uploader

This video uploader and playback app is built with Next.js and api.video, the video first API.

Demo

https://with-apivideo.vercel.app/videos

Deploy your own

Deploy the example using Vercel:

How to use

Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:

npx create-next-app --example with-apivideo

yarn create next-app --example with-apivideo

pnpm create next-app --example with-apivideo

Deploy it to the cloud with Vercel (Documentation).

Getting started

1. Create an api.video free account

Go to dashboard.api.video, log in or create a free account.
You can choose to stay in sandbox and have watermark over your videos, or enter in production mode and take advantage of all the features without limitations.

2. Get you API key

Once in the dashboard, find your API keys directly in the /overview or navigate to /apikeys with the "API Keys" button in the side navigation.
Copy your API key, and paste it in .env.local.example as value for API_KEY.
Rename .env.local.example to .env.local.
Install the packages by running npm install, yarn install or pnpm install.
You can now try the application locally by running npm run dev, yarn dev or pnpm dev from the root directory.

3. Deployment

First, push your app to GitHub/GitLab or Bitbucket
Then, go to Vercel and import your new repository.
Add an environment variable with name API_KEY and your API key for value.
Click on deploy 🎉