id.420129/invidious-setup
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
This repository has been archived on 2025-06-03. You can view files and clone it, but you cannot make any changes to its state, such as pushing and creating new issues, pull requests or comments.
17 commits 1 branch 0 tags 51 KiB
Find a file
Exact
Minecon724 4f7db218b5
 Fix reset.sh
2025-04-30 13:43:54 +02:00
invidious@23ff6135bb Initial commit 2025-03-29 15:51:31 +01:00
.gitmodules Initial commit 2025-03-29 15:51:31 +01:00
botPolicy.json Reintroduce nginx 2025-04-30 13:36:20 +02:00
config-refresh.yaml Reintroduce nginx 2025-04-30 13:36:20 +02:00
config.yaml Reintroduce nginx 2025-04-30 13:36:20 +02:00
docker-compose.yml Reintroduce nginx 2025-04-30 13:36:20 +02:00
hard-reset.sh Reintroduce nginx 2025-04-30 13:36:20 +02:00
nginx.conf Reintroduce nginx 2025-04-30 13:36:20 +02:00
README.md Update README 2025-04-30 13:43:23 +02:00
reset.sh Fix reset.sh 2025-04-30 13:43:54 +02:00

README.md

Invidious, how I do it.

  1. Clone with submodules!!! (--recursive)
  2. Fill in placeholders
  3. Schedule:
    • reset.sh restarts Invidious.
    • hard-reset.sh updates and restarts everything. I suggest to schedule only this, daily.

Placeholders:

  1. 192.168.81.2 in docker-compose.yml
  2. In both config.yml and config-refresh.yml:
    • hmac_key - see below
    • invidious_companion_key - see below
    • companions - see here
    • (optional) http_proxy
    • (optional) modified_source_code_url

You can generate keys with:

openssl rand -hex 8

config.yml vs config-refresh.yml

There are two Invidious instances (or, precisely, classes)

One handles "background work," that is refreshing stuff, like user subscriptions. It's not exposed to users.
The other (replicated) is exposed to users and handles user stuff. It's what you see.