No description
src/invidious_export_server | ||
.env.example | ||
.gitignore | ||
Containerfile | ||
entrypoint.sh | ||
poetry.lock | ||
pyproject.toml | ||
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