kasper.space / vidl-v1
[READ-ONLY] Mirror of https://github.com/probablykasper/vidl-v1. Server/website/chrome extension for downloading video/audio v1.vidl.kasper.space
audio browser-extension chrome chrome-extension downloader extension video website
0
Fork 0

Configure Feed

Select the types of activity you want to include in your feed.

JavaScript 9.9%
Sass 2.1%
CSS 1.6%
HTML 1.3%
Pug 1.3%
Dockerfile 0.1%
Other 83.7%
142 1 0

Clone this repository

https://tangled.org/kasper.space/vidl-v1 https://tangled.org/did:plc:5hsffbrxee34l5l5ozmznlra
git@tangled.org:kasper.space/vidl-v1 git@tangled.org:did:plc:5hsffbrxee34l5l5ozmznlra

For self-hosted knots, clone URLs may differ based on your setup.


Download tar.gz Download .zip
README.md

vidl#

Video/audio download site

Note: The repo is unmaintained and the server is not online.

Screenshot

Website#

The website source code is located in the website folder.

Get started#

  • Install NPM
  • npm install: install the dependencies.
  • npm run build-prod: build the website. The output is located inside the docs folder, so it can be hosted on GitHub Pages for free.
  • npm run build-dev: Just like build-prod, but for development (it watches for changes).
  • In config.js, you'll find the websocket URLs that the website connects to. One URL for local development and one for production. In dev mode, the website is hosted on localhost:8080. You can change the port in config.js.

Server#

Get started#

  • Install Docker
  • docker-compose build: Build the thing and install the NPM dependencies. This will build youtube-dl from source, so it will take a while.
  • npm run prod: Starts the server in production mode. All it does is run VIDL_ENV=prod docker-compose up
  • npm run dev: Starts the server in dev mode. All it does is run VIDL_ENV=dev docker-compose up

Browser extension#

Note: Only Chrome is officially supported at the moment. The browser extension source code is located in the browser-extension folder.

Get started#

  • Install NPM
  • npm install: install the dependencies.
  • npm run build-prod: build the website. It outputs a chrome folder that can be added as an unpackaged extension, and a chrome.zip file that can be added as a real extension.
  • npm run build-dev: Just like build-prod, but for development (it watches for changes).
  • In config.js, you'll find the websocket URLs that the website connects to. One URL for local development and one for production.