NeskireDK c0a6587d52 Store the fork's settings in Postgres, overriding the config
Production feeds the config through INVIDIOUS_CONFIG, so a config.yml
written at runtime is thrown away on the next restart. The fork's own
settings therefore need a home the admin can write to: a key/value table
arik_settings, one row per setting.

- The environment config is parsed and validated first and seeds every
  value; a stored row then overrides the value of its own key. A key
  without a row keeps the environment value.
- Applied at boot right after the table integrity check, so Config.check
  still fails closed on a bad environment config while a bad database
  row only loses its own override: decoding reports the reason and the
  environment value stands.
- Validation lives in ArikSettings and is pure, so the admin UI can
  refuse an entry before it is stored. It refuses what hurts later: a
  CIDR range in trusted_proxies (Config.check exits on it at the next
  boot), header auth enabled with no trusted proxy at all, and callback
  origins that are not a bare scheme+host+port.
- Two new trusted_header_auth fields are declared here and wired up in
  the commits that follow: password_self_service and
  auto_approve_token_callbacks.

The table is created both by a migration and by check_integrity, so
instances on either path get it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-13 06:14:01 +02:00
2024-10-13 23:57:29 +02:00
2021-07-24 20:48:30 +02:00
2017-11-23 01:48:55 -06:00
2026-08-02 18:21:18 -04:00
2026-08-04 21:01:38 -04:00
2018-01-28 11:32:40 -06:00
2026-08-04 21:01:38 -04:00
2020-05-26 18:02:21 +00:00

Invidious logo

Invidious

License: AGPLv3 Build Status GitHub commits GitHub issues GitHub pull requests Translation Status

An open source alternative front-end to YouTube

Website  •  Instances list  •  FAQ  •  Documentation  •  Contribute  •  Donate

Chat with us:
Matrix Libera.chat (IRC)
Fediverse: @invidious@social.tchncs.de
E-mail

Screenshots

Player Preferences Subscriptions

Features

User features

  • Lightweight
  • No ads
  • No tracking
  • No JavaScript required
  • Light/Dark themes
  • Customizable homepage
  • Subscriptions independent from Google
  • Notifications for all subscribed channels
  • Audio-only mode (with background play on mobile)
  • Support for Reddit comments
  • Available in many languages, thanks to our translators

Data import/export

  • Import subscriptions from YouTube, NewPipe and FreeTube
  • Import watch history from YouTube and NewPipe
  • Export subscriptions to NewPipe and FreeTube
  • Import/Export Invidious user data

Technical features

  • Embedded video support
  • Developer API
  • Does not use official YouTube APIs
  • No Contributor License Agreement (CLA)

Quick start

Using Invidious:

Hosting Invidious:

Documentation

The full documentation can be accessed online at https://docs.invidious.io/

The documentation's source code is available in this repository: https://github.com/iv-org/documentation

Extensions

We highly recommend the use of Privacy Redirect, a browser extension that automatically redirects YouTube URLs to any Invidious instance and replaces embedded YouTube videos on other websites with Invidious.

The documentation contains a list of browser extensions that we recommended to use along with Invidious.

You can read more here: https://docs.invidious.io/applications/

Contribute

Code

  1. Fork it ( https://github.com/iv-org/invidious/fork ).
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Stage your files (git add .).
  4. Commit your changes (git commit -m 'Add some feature').
  5. Push to the branch (git push origin my-new-feature).
  6. Create a new pull request ( https://github.com/iv-org/invidious/compare ).

Translations

We use Weblate to manage Invidious translations.

You can suggest new translations and/or correction here: https://hosted.weblate.org/engage/invidious/.

Creating an account is not required, but recommended, especially if you want to contribute regularly. Weblate also allows you to log-in with major SSO providers like GitHub, GitLab, BitBucket, Google, ...

Projects using Invidious

A list of projects and extensions for or utilizing Invidious can be found in the documentation: https://docs.invidious.io/applications/

Liability

We take no responsibility for the use of our tool, or external instances provided by third parties. We strongly recommend you abide by the valid official regulations in your country. Furthermore, we refuse liability for any inappropriate use of Invidious, such as illegal downloading. This tool is provided to you in the spirit of free, open software.

You may view the LICENSE in which this software is provided to you here.

  1. Limitation of Liability.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Description
Invidious is an alternative front-end to YouTube
Readme AGPL-3.0 72 MiB
Languages
Crystal 73.6%
HTML 12.8%
JavaScript 7.9%
CSS 2.5%
Python 1.5%
Other 1.7%