- 1 Post
- 5 Comments
Joined 3 months ago
Cake day: May 7th, 2026
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Transparent_knoll@awful.systemsto
Gaming@beehaw.org•Has there ever been a game whose name was intentionally suffixed with "2" despite no original game? lol
41·17 days agoGoat simulator 3 exists, despite there being no Goat simulator 2.
Transparent_knoll@awful.systemsto
World News@lemmy.world•World Cup fans frustrated by 'confusing and expensive' tipping culture in USEnglish
1342·1 month agoKeller said he’s changed the system so customers with reservations have to pre-pay for drinks, including a service charge. “It’s just to protect our staff,”
So, customers not paying tips is forcing the business to pay a living wage, as well as incorporate wages into the price model of products rather than leave it as a hidden morality tax?
Oh, The horror. /s
Transparent_knoll@awful.systemsto
World News@lemmy.world•Bill Gates says Epstein sought to blackmail him over extramarital affairsEnglish
3·1 month agoHaha, you ain’t wrong, though I don’t think the girls on the island were given much of a choice to be fair.



I’d recommend creating a gateway service. You basically have two routes, managed gateways or self hosted using a rented virtual private server (VPS).
Managed
These are services that are managed by companies, that allow the setup of VPN tunnels with a public access point. Some examples are:
There’s not too much to say on this approach, it’s easy to setup, but depending on the level of ownership you’re looking for, it may or may not be the correct route for you.
Self-Hosted via VPS
Reason you want to use a VPS as the gateway, is so that at no point is your home server exposed to the public. Instead, any potentially malicious actions (which is an inevitably when creating public facing services ) are directed at your VPS rather than your actual server.
There are a few different options, some examples are:
Both of these are designed to implement an access point (your VPS) and any number of devices to proxy (your homeserver). They are built upon wireguard, and are feature rich.
Personally, I opted for a more lightweight approach using selfhosted-gateway, which is definitely a bare bones Reverse Proxy over VPN, designed specifically for exposing docker containers on your homeserver. Much like the other options, it’s built upon wireguard VPN. Theres no UI (which is why imo it’s perfect for a tiny VPS), just a simple MAKE command thats run from your homeserver and generates the required docker compose files, then once spun up creates the link between your VPS and exposes the appropriate docker container.