gobbling871

joined 1 year ago
[–] gobbling871@lemmy.world 6 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] gobbling871@lemmy.world 2 points 1 year ago (1 children)

Comments inside the docker-compose.yml files?

[–] gobbling871@lemmy.world 1 points 1 year ago (2 children)

They successfully went after Vanced 2 years ago so it's shouldn't be too far fetched for them.

[–] gobbling871@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

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).

[–] gobbling871@lemmy.world 8 points 1 year ago

Backblaze b2, borgbase.com. There are also programs like dejadup that will let you backup to popular cloud drives. The alternatives are limitless.

[–] gobbling871@lemmy.world 5 points 1 year ago

This sounds good just saying it but in practice it's not possible for AI to fully replace these types of jobs.

spoilerAt least not yet.

[–] gobbling871@lemmy.world 1 points 1 year ago

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
[–] gobbling871@lemmy.world 0 points 1 year ago (2 children)

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.

[–] gobbling871@lemmy.world 2 points 1 year ago

Haha. Said the hoader with tonnes of content he's never going to finish watching.

 

Basically have watchtower monitor and update containers whenever new images are released. I've recently noticed that with searxng (using redis as db), hosted through nginx proxy manager, will have a steady downtime of about 15mins post update then come back online.

This is extremely frequent for searxng's case as I have watchtower run every day and my preferred way of running most of my containers is with the latest tag. The way out of this downtime in my experience is a restart of NPM which brings back the searxng service.

I'm looking for a way to automate a restart of the NPM container after a successful update of searxng's container.

I have checked the docs for watchtower, and the lifecycle hooks (a way to run sh scripts pre/post update) are able to run only from the applied container and not from the host system.

view more: next ›