𝘋𝘪𝘳𝘬

Somewhere between Linux woes, gaming, open source, 3D printing, recreational coding, and occasional ranting.

🔗 Me, but elsewhere

🇬🇧 / 🇩🇪

  • 0 Posts
  • 19 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle


  • depending on how you look

    … and even more where you cross the border. If I want to go (like in “just walk there”) from Poland to Germany, I could use this bridge for example:

    It’s really just an ordinary bridge across a river, no border patrol, no ID check, nothing. Just walk from one country into another.

    Or if I want to cross the border from Germany to France, I could just use that publicly accessible hiking path:

    (Seen from French side, the barrier where the people sit is the whole border crossing point.) And this bridge with a view brings you from France to Spain.

    Except border check points you’ll find luxury housing on French side and commercial buildings (stores and some warehouses) on Spain side.

    At no point in that imaginary journey (now that I think about it, this would make a great road trip with hiking parts) you need your ID card when you travel to another country.

    Long story short: It’s really easy to cross borders in the EU.


  • I live in the EU and thus I can travel pretty far away without having to ever show my ID card. Maybe it’s just personal experience but whenever I had to show it, no-one cared about it wasn’t valid anymore.

    Another trick is acting stupid: “Oh, thank you! I didn’t notice! When would a normal person check that, eh? 🙂 … Right on next Monday I’ll going to renew it!” and then hasta la vista, we won’t meet ever again anyways.

    The next time I have to renew it, is in 2031. I guess I won’t renew it till 2040.














  • How do you handle SSL certs and internet access in your setup?

    I have NPM running as “gateway” between my LAN and the Internet and let handle it all of my vertificates using the built-in Let’s Encrypt features. None of my hosted applications know anything about certificates in their Docker containers.

    As for your questions:

    1. You can and should – it makes managing the applications much easier. You should use some containerization. Subdomains and correct routing will be done by the reverse proxy. You basically tell the proxy “when a request for foo.example.com comes in, forward it to myserver.local, port 12345” where 12345 is the port the container communicates over.
    2. 100% depends on your use case. I purchased a domain because I host stuff for external access, too. I just have my setup to report it’s external IP address to my domain provider. It basically is some dynamic DNS service but with a “real domain”. If you plan to just host for yourself and your friends, some generic subdomain from a dynamic DNS service would do the trick. (Using NPMs Let’s Encrypt configuration will work with that, too.)
    3. You can’t. Every georestricting can be circumvented. If you want to restrict access, use HTTP basic auth. You can set that up using NPM, too. So users authenticate against NPM and only when it was successful,m the routing to the actual content will be done.
    4. You might want to look into Cloudflare Tunnel to hide your real IP address and protect against DDoS attacks.
    5. No 🙂