Recipes VS openvpn-client

For recipes, I highly recommend Tandoor

Release 1.4.8 significantly improved lots of UIs, adding better navigation and dedicated layouts to mobile versions and cleaning up lots of old pages

Tandoor Was developed initially for that, to import your pdf collection of recipes. It has now evolved to be much more than that and personally prefer it to Mealie, could be worth trying!

the downside is, that it's a bit more complicated. i haven't been able to get it to properly show the images of the recipees after i imported them. this is my Github Issue, maybe i've been able to resolve it by the point you're reading this.

Tandoor Recipes is used every day by everyone in my house.

I'm curious - how does Mealie compare to Tandoor?

I use dperson/openvpn-client, which seems to do the trick for the most part. Ive got several packages that route through it using network_mode: "service:openvpn".

Gluetun has an integrated killswitch: https://github.com/qdm12/gluetun

I used to use https://github.com/dperson/openvpn-client which has a killswitch as well.

By kill-switch I mean iptables rules that don't let anything out if there's no VPN interface up. So you don't run the risk of leaking torrent stuff through your plain-text connection.

One of my Pi servers running a series of Docker services was taken out a few months back because an apt upgrade changed the compilation target of time_t causing me to have to spend a week untangling a web of dependencies to revert to an older version of musl.

I just tested the https://github.com/dperson/openvpn-client to use my NordVPN account and could get it working, the container connects succesfully! Can I somehow share this connection to other LAN devices (eg my TV) where I cant't install a VPN client?

I have gone down a rabbit hole today trying to route all Docker container traffic through OpenVPN. Previously I have used dperson/openvpn-client, but I would prefer to run OpenVPN directly on the host. With the VPN up on the host, the Docker containers make use of the VPN connection but if it drops they continue without it. Ideally there would be a kill switch to prevent this from happening.

I am looking to use my protonvpn subscription to use with an OpenVPN container (this one), but the documentation on both Protonvpn and the repo is pretty light on how to use it.

Hey there, I successfully managed to run this OpenVPN docker Container on my DS218+. I then connected another container to use this OpenVPN container as a network. Everything works like a charm.

OpenVPN client to route my illicit content through Pakistan (CyberGhost paid VPN)

As someone who's currently using dperson/openvpn-client with a Cyberghost VPN, what are the advantages of this container?

services: vpn: container_name: vpn image: dperson/openvpn-client # cap_add, security_opt, and volume required for the image to function cap_add: - net_admin environment: TZ=Europe/London read_only: true tmpfs: - /run - /tmp restart: unless-stopped security_opt: - label:disable stdin_open: true tty: true volumes: - /dev/net:/dev/net:z - ./vpn:/vpn # You will need to change this, read https://github.com/dperson/openvpn-client # -r is your CIDR network (I specify two to allow my other docker containers in) # -f should be set to your VPN port, all other ports get firewalled # -p is for port forwarding, so your torrent port forwards work. command: '-r 192.168.1.0/24 -r 172.19.0.0/16 -f 1302 -p 23009' # Since all the containers using the VPN share the same network interface # Ports forwarded here reach the deluge container ports: - 58846:58846 - 8112:8112 sysctls: - net.ipv6.conf.all.disable_ipv6=0 # Remove this if you don't want IPv6