ansible-easy-vpn VS cuelm

I would put this behind a VPN to keep it private. I have used this[0] Wireguard setup before, which takes the grunt work out of configuring everything.

[0] https://github.com/notthebee/ansible-easy-vpn

This Wireguard VPN "package": here

https://github.com/notthebee/ansible-easy-vpn can help with the configuration.

Use this script to deploy Wireguard VPN server. https://github.com/notthebee/ansible-easy-vpn https://www.youtube.com/watch?v=SMF301vQqJo

I use Wireguard. Here is a nice tutorial with the Ansible playbook. https://www.youtube.com/watch?v=SMF301vQqJo https://github.com/notthebee/ansible-easy-vpn

I have been using Jellyfin for a while now, but recently changed my setup a little. My server is now behind a VPN created with this script: https://github.com/notthebee/ansible-easy-vpn. I used to have port forwarding setup with my previous VPN provider, and then used nginx on the same server that Jellyfin was running on for a reverse proxy. This allowed me to access my server outside my home, but also use a VPN. Now (assuming the client device isn't connected to the same VPN) I can't do that. It seems that if I edit the BunkerWeb .env file I should be able to get a similar setup, but I can't figure out how. The Jellyfin documentation only discusses nginx and not what I'm using.

Server (VPS with this guide: https://github.com/notthebee/ansible-easy-vpn):

I have used this setup and initially the speed was nearly full bandwidth, but not anymore.

We've started working on a tool to use CUE to create a single config space across TF, Helm, and other tools in the devops space.

https://github.com/hofstadter-io/cuelm

Our hypothesis is that a unified config space across our industry will bring many benefits.

Our open questions are largely around whether we

(1) replace / alternative

(2) just a skin, still same reconciliation loop from the tools

(3) replace, but support existing modules & charts

Thanks for the share! Very timely

We are in the process of introspecting TF to produce CUE schemas. Maybe this can help us cuetify user TF as well

if you are curious: https://github.com/hofstadter-io/cuelm (it has expanded in scope since inception to include the likes of TF and other areas of e2e CI)