Update README

This commit is contained in:
weidenwiesel
2025-10-10 15:19:16 +02:00
parent 11b3915483
commit 4705d8e686
+6 -2
View File
@@ -18,8 +18,9 @@ If you already have an instance using the official invidious, you CANNOT simply
This is due to the the following changes which I implemented to improve the performance and reliability of my instance:
- Removal of materialized views as subscription tables in PostgreSQL (see https://git.nerdvpn.de/NerdVPN.de/invidious/src/branch/nerdvpn/patches/invidious/011-remove-psql-mat-views.patch)
- Redis as video cache (see https://git.nerdvpn.de/NerdVPN.de/invidious/src/branch/nerdvpn/patches/invidious/010-use-redis-for-video-cache.patch)
- Multiple companion backends (see https://git.nerdvpn.de/NerdVPN.de/invidious/src/branch/nerdvpn/patches/invidious/0003-multiple-companion-backends.patch)
- Redis as video cache (see https://git.nerdvpn.de/NerdVPN.de/invidious/src/branch/nerdvpn/patches/invidious/0007-redis-for-video-cache.patch)
- Removal of materialized views as subscription tables in PostgreSQL (see https://git.nerdvpn.de/NerdVPN.de/invidious/src/branch/nerdvpn/patches/invidious/0008-remove-psql-materialized-views.patch)
If you NEVER used Invidious before, you can safely start with my fork, but you won't be able to switch to upstream Invidious at all.
@@ -37,6 +38,9 @@ You'll have to set these up yourself:
# For public instances
First, read EVERYTHING on here: https://docs.invidious.io/
If you want to host a public instance, you should acuire a few VPN/proxies to bypass blockage from YouTube. Otherwise, your instance (and your server IP) will simply get blocked by YouTube after a few hours max.
I will not give any recommendations here because this is something you should research and manage for yourself.