dave/site
1
0
Fork 0
mirror of https://github.com/davegallant/davegallant.github.io.git synced 2025-08-07 00:58:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: e669eb8bd70b18b4a83d3c6786eef065109c44c0

Browse Source
This commit is contained in:
davegallant
2024-07-20 12:03:24 +00:00
parent 598e2e205a
commit 2e1fd2b7ac
74 changed files with 96 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
js/flexsearch.95f8339f006f50d03b13d2990a2d82bfebb8ff305eb82244913e22ae43e3d6d28dc5fcfc69cb344bcc7824e30c6f1bbf6af6c2e49d8878378fc6040e70a51571.js → js/flexsearch.302b31b98eee596733b00ef3497449a8825caa3d4dc4e416dd3e2b3f4f4264d767bb05cb0a1b5c606cd19ff62bf7344f3ec5c8d4f9b8d0409731bf83287d2369.js
View File

@@ -62,8 +62,8 @@ Hosting invidious# The quickest way to get invidious up is with docker-compose a
I made a few modifications, and ended up with:
version: "3" services: invidious: image: quay.io/invidious/invidious restart: unless-stopped ports: - "0.0.0.0:3000:3000" environment: INVIDIOUS_CONFIG: | db: dbname: invidious user: kemal password: kemal host: invidious-db port: 5432 check_tables: true healthcheck: test: wget -nv --tries=1 --spider http://127.0.0.1:3000/api/v1/comments/jNQXAC9IVRw || exit 1 interval: 30s timeout: 5s retries: 2 depends_on: - invidious-db invidious-db: image: docker.io/library/postgres:14 restart: unless-stopped volumes: - postgresdata:/var/lib/postgresql/data - ./config/sql:/config/sql - ./docker/init-invidious-db.sh:/docker-entrypoint-initdb.d/init-invidious-db.sh environment: POSTGRES_DB: invidious POSTGRES_USER: kemal POSTGRES_PASSWORD: kemal healthcheck: test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"] volumes: postgresdata: After invidious was up and running, I installed Tailscale on it to leverage its MagicDNS, and I’m now able to access this instance from anywhere at http://invidious:3000/feed/subscriptions.
Redirecting YouTube links# I figured it would be nice to redirect existing YouTube links that others send me, so that I could seamlessly watch the videos using invidious.
I went looking for a way to redirect paths at the browser level. I found the lightweight proxy requestly, which can be used to modify http requests in my browser. I created the following rules:
Now the link https://www.youtube.com/watch?v=-lz30by8-sU will redirect to http://invidious:3000/watch?v=-lz30by8-sU
I went looking for a way to redirect paths at the browser level. I found the lightweight proxy Redirector, which can be used to modify http requests in the browser. I created the following redirect (exported as json):
{ "redirects": [ { "description": "youtube to invidious", "exampleUrl": "https://www.youtube.com/watch?v=-lz30by8-sU", "exampleResult": "http://invidious:3000/watch?v=-lz30by8-sU", "error": null, "includePattern": "https://*youtube.com/*", "excludePattern": "", "patternDesc": "Any youtube video should redirect to invidious", "redirectUrl": "http://invidious:3000/$2", "patternType": "W", "processMatches": "noProcessing", "disabled": false, "grouped": false, "appliesTo": [ "main_frame" ] } ] } Now the link https://www.youtube.com/watch?v=-lz30by8-sU will redirect to http://invidious:3000/watch?v=-lz30by8-sU
I’m still looking for ways to improve this invidious setup. There doesn’t appear to be a way to stream in 4K yet.
`}).add({id:4,href:"/blog/virtualizing-a-router-with-pfsense/",title:"Virtualizing my router with pfSense",description:`My aging router has been running OpenWrt for years and for the most part has been quite reliable. OpenWrt is an open-source project used on embedded devices to route network traffic. It supports many different configurations and there exists a large index of packages. Ever since I’ve connected some standalone wireless access points, I’ve had less of a need for an off-the-shelf all-in-one wireless router combo. I’ve also recently been experiencing instability with my router (likely the result of a combination of configuration tweaking and firmware updating). OpenWrt has served me well, but it is time to move on!
`,content:`My aging router has been running OpenWrt for years and for the most part has been quite reliable. OpenWrt is an open-source project used on embedded devices to route network traffic. It supports many different configurations and there exists a large index of packages. Ever since I’ve connected some standalone wireless access points, I’ve had less of a need for an off-the-shelf all-in-one wireless router combo. I’ve also recently been experiencing instability with my router (likely the result of a combination of configuration tweaking and firmware updating). OpenWrt has served me well, but it is time to move on!