Neat. But it’s kind of concerning to see yet another OSS project hitch it’s community resourcing to Discord.
quaff
joined 3 years ago
I’ve switched from Quad9 to Mullvad DNS a month ago, and I’ve been noticing some domains aren’t resolving. Domains that shouldn’t be blocked. It feels like Mullvad’s rules are extra restrictive.
The key for me was being told: it’s okay to ride (to hold) the clutch a little before/during/after you’re switching gears.
Are there any updates regarding microphone and Touch ID support in this release?
Are there any updates regarding microphone and Touch ID support in this release?
I removed mine since I moved away from Gitlab. There's other comments with working docker composes, but here's the latest working version of mine if you're interested:
services:
gluetun:
image: ghcr.io/qdm12/gluetun:latest
container_name: gluetun
# line above must be uncommented to allow external containers to connect. See https://github.com/qdm12/gluetun/wiki/Connect-a-container-to-gluetun#external-container-to-gluetun
restart: always
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- ./data:/gluetun
environment:
## ProtonVPN Wireguard
- VPN_SERVICE_PROVIDER=custom
- VPN_TYPE=wireguard
- VPN_ENDPOINT_IP=${WIREGUARD_ENDPOINT_IP}
- VPN_ENDPOINT_PORT=${WIREGUARD_ENDPOINT_PORT}
- WIREGUARD_PUBLIC_KEY=${WIREGUARD_PUBLIC_KEY}
- WIREGUARD_PRIVATE_KEY=${WIREGUARD_PRIVATE_KEY}
- WIREGUARD_ADDRESSES=${WIREGUARD_ADDRESSES}
- TZ=Etc/UTC
ports:
- ${QBITTORRENT_EXPOSED_WEBUI_PORT}:8080/tcp # qBittorrent Web UI
qbittorrent:
# https://docs.linuxserver.io/images/docker-qbittorrent
build: .
container_name: qbittorrent
restart: always
volumes:
- ./config:/config
# using download path as mount so other services can play nice
- ${QBITTORRENT_DOWNLOAD_PATH}:${QBITTORRENT_DOWNLOAD_PATH}
- ${QBITTORRENT_THEMES_PATH}:/themes
environment:
# https://github.com/linuxserver/docker-qbittorrent#umask-for-running-applications
- PUID=${QBITTORRENT_WRITE_UID}
- PGID=${QBITTORRENT_WRITE_GID}
- UMASK=0002
- TZ=Etc/UTC
- WEBUI_PORT=8080
network_mode: "service:gluetun"
depends_on:
gluetun:
condition: service_healthy
portcheck:
image: eiqnepm/portcheck:latest
container_name: portcheck
restart: always
environment:
- QBITTORRENT_PORT=6881
- QBITTORRENT_WEBUI_PORT=8080
- QBITTORRENT_WEBUI_SCHEME=http
- QBITTORRENT_USERNAME=admin
- QBITTORRENT_PASSWORD=${QBITTORRENT_ADMIN_PASSOWRD}
- TIMEOUT=300
- DIAL_TIMEOUT=5
network_mode: "service:gluetun"
depends_on:
qbittorrent:
condition: service_healthy
That’s great to hear! I’m glad you found the mismatched data 🙏🙏🙏 hopefully finding the root issue doesn’t cost you too many cycles 🫡
Caught it again! Seems to be happening quite frequently now. I spot it by looking for mismatched community icons.
It’s happened on a previous beta, I can’t remember if it was the last one or the one before that.
I had it happen again yesterday. Not related to those two communities. Same issues, the feed showed one thing, but with mixed data (I think the community thumbnail was displaying the post that actually loads). I’ll make another video when I see it again 🙏
The TenForward community I sub to is favourited, other than that, no filters or anything done to it.
Pretty simple to switch (if you have a little docker experience). Create a folder (e.g. ./postgres), add the folder as a volume in the postgres portion of the compose file (maybe something like /db), then run just the database with newly mounted folder, shell in, and copy everything from the Postgres folder to this new folder. After that, swap mounts so the new folder is used as Postgres db and you’re good. If something went wrong, the pgdata volume is still there to switch back to.
Neat. But it’s kind of concerning to see yet another OSS project hitch it’s community resourcing to Discord.