id.420129/invidious-export-server
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions
No description
5 commits 1 branch 0 tags 61 KiB
Find a file
Exact
Minecon724 c218e5a234
 Add hardcoded contact info
2025-06-15 15:41:57 +02:00
src/invidious_export_server Add hardcoded contact info 2025-06-15 15:41:57 +02:00
.env.example Work behind reverse proxy 2025-06-15 15:34:32 +02:00
.gitignore Initial commit 2025-06-15 13:24:17 +02:00
Containerfile Work behind reverse proxy 2025-06-15 15:34:32 +02:00
entrypoint.sh Initial commit 2025-06-15 13:24:17 +02:00
poetry.lock Initial commit 2025-06-15 13:24:17 +02:00
pyproject.toml Work behind reverse proxy 2025-06-15 15:34:32 +02:00
README.md Add guide to README 2025-06-15 15:36:52 +02:00

README.md

Preparation

You can connect directly to the Invidious database.

Only the following tables are used and must be kept:

  • playlist_videos
  • playlists
  • session_ids
  • users

You can delete the other ones.

For example, if you're exporting the database:

pg_dump -U kemal -t playlist_videos -t playlists -t session_ids -t users invidious -Fc -Z3 > invidious.sql

This saves 90% of storage compared to running pg_dump without args, in my case 432M -> 25M

Then:

cat invidious.sql | pg_restore -U kemal -d invidious

Environment variables

See the .env.example file

Health check

A /health endpoint is provided that always returns OK