![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Comments inside the docker-compose.yml
files?
Comments inside the docker-compose.yml
files?
They successfully went after Vanced 2 years ago so it’s shouldn’t be too far fetched for them.
Maybe give cloudflared a try. Works for me even with nextcloud’s ssl (don’t think there’s a way to start NC without the self-signed cert). Couldn’t get it to work with NPM (I admittedly don’t know much about nginx) so I brought in the big gun(s).
deleted by creator
Backblaze b2, borgbase.com. There are also programs like dejadup that will let you backup to popular cloud drives. The alternatives are limitless.
This sounds good just saying it but in practice it’s not possible for AI to fully replace these types of jobs.
At least not yet.
Major oof
No minimum requirements. And here you go:
#version: "3.8"
services:
invidious:
image: quay.io/invidious/invidious:latest
restart: unless-stopped
security_opt:
- no-new-privileges
container_name: invidious
stop_grace_period: 3s
ports:
- 127.0.0.1:3000:3000
environment:
INVIDIOUS_CONFIG: |
db:
dbname: invidious
user: invidious
password: superstrongpassword491
host: postgres
port: 5432
check_tables: true
popular_enabled: true
login_enabled: false
statistics_enabled: true
hsts: true
hmac_key: *PICK-A-LONG-RANDOM-STRING*
https_only: true
external_port: 443
use_quic: true
database_url: postgres://invidious:superstrongpassword491@postgres/invidious?auth_methods=md5,scram-sha-256
force_resolve: ipv4
domain: *your.domain.com*
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:
- postgres
postgres:
image: postgres:15-alpine
container_name: postgres
security_opt:
- no-new-privileges
restart: always
# purposefully excluded volumes section
# the database will reset on recreate
environment:
POSTGRES_DB: invidious
POSTGRES_USER: invidious
POSTGRES_PASSWORD: superstrongpassword491
healthcheck:
test: pg_isready -U invidious -d invidious
interval: 10s
timeout: 5s
retries: 5
I’ve hosted invidious relatively easy for a while now. Simple UI and just works. If anyone needs my compose and config setup, reply and I’ll post it.
Haha. Said the hoader with tonnes of content he’s never going to finish watching.
deleted by creator
They provide the best balance for efficiency. Not too powerful enough to be a workhorse and not to weak to run multiple simple applications/services. NUCs are great in that they come with hardware video acceleration tech that’s highly optimized for media transcoding.
What is exactly false about my statement?
I was in the same boat many years ago with Chrome until I discovered how to migrate the passwords to Bitwarden.
Nah. The real advice here is use uBlock Origin and control your cookies. Both Chrome and Firefox contains things that go against user privacy.
You don’t get any network isolation with this approach vs a service running in its own dedicated virtual network. Just for this reason, I think Wireguard as a VPN access to other local services is insecure.
I always see guys swearing by Wireguard for VPN access as a security measure and seems to me like if someone unauthorized gets your public key, they have access to the kingdom.
For accessing your VPN network outside of your LAN, there’s the shadowsocks option in the gluetun wiki.
I use restic (and dejadup just to be safe) backing up to multiple cloud storage points. Among these cloud storage points are borgbase.com, backblaze b2 and Microsoft cloud.
It’s a vpn client on steroids that creates a VPN network (based on your provider) which you can then use to run docker containers inside of, as well as create http & shadowsocks proxies for your VPN network etc.