Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Wireguard gives my service servers their own internal IP for the gateway to reference (nothing fancy done with it, no iptables modifications like you may see on other guides), and I use NGINX for the game server proxying, specifically linuxserver's nginx container. I love Caddy, but even with caddy-l4 I couldn't get it working right for Valheim (and thus UDP), but NGINX worked real quick.
For nginx, if you don't want to deal with Docker, you can probably just follow their quick start guide, installing it on the gateway/proxy server. For the config file, if chucking on a "stream" block like I showed onto the default file that exists on install doesn't cut it, you can always reference linuxserver's default config file. Again, all I did was nuke the "http" block since I wasn't using it.
Related posts
- Let's Embed a Go Program into the Linux Kernel
- keepsecret.py: a simple way to encrypt secret files in your repository
- Show HN: Is_ready – Wait for many services to become available – 0 Dependencies
- Process Compose: flexible scheduler to manage non-containerized apps
- Dagger: Programmable open source CI/CD engine that runs pipelines in containers