• 0 Posts
  • 21 Comments
Joined 9 months ago
cake
Cake day: October 4th, 2023

help-circle



  • If you have an interest in Arch, I’d recommend starting with a derivative distro like EndeavourOS. It’ll give you an easy installation process and a desktop that’s ready to use.

    Then just use it as your daily driver. You’ll eventually run into the occasional issue when package X or Y upgrades and breaks something, learn to fix that, and eventually learn the “ins and outs” of Arch. That’s how I started, I went from Mint to Antergos, used that for a while, then when Antergos was discontinued (RIP) I converted my install to “pure” Arch and never looked back.


  • RustDesk sort of fits the bill. It’s open-source, has 2FA, can be self-hosted (but not needed), the client runs on anything, but the main issue here is that no amount of workarounds will make an untrusted machine any less untrusted, you’re essentially extending the display and input from a dubious machine into your own.

    If you’re really worried about the security aspect, my suggestion would be to only use your phone as the client, and if you need to do anything more complex, use a Bluetooth keyboard connected to it. There are some foldable keyboards that don’t take too much space and are not terrible.










  • antsu@lemmy.wtftoLinux@lemmy.mlFriendly reminder
    link
    fedilink
    arrow-up
    13
    ·
    6 months ago

    Timeshift with BTRFS kicks ass. I have mine set for daily snapshots, retained for a week. Only the changes between snapshots are stored, so the extra disk usage is minimal, and easily justified by the peace of mind in case of fuck-ups or broken updates.



  • antsu@lemmy.wtftoLinux@lemmy.mlZFS Swap on Linux
    link
    fedilink
    arrow-up
    1
    ·
    7 months ago

    I don’t have the source right now, but I had the same idea not long ago, and the tl;dr is swap on a zvol is a very bad idea. If your system ever runs low on memory and actually needs to do heavy swapping, you’re setting yourself up for a catastrophe.





  • This looks about right, I have a similar setup for unauthenticated services here, with the difference that I’m using NGINX Proxy Manager instead of Caddy. The things I would try/check are:

    • Make sure you’ve enabled the proxy provider in the local outpost config in Authentik.
    • Declare a common network between the two containers, so that they can communicate without having to go out through the host’s IP. This way you can reference the VS Code container directly by its service name in Authentik.
    • I’m not familiar with Caddy, but I would also try changing the code.test.example.com entry to point directly to Authentik’s IP and port (in other words, both entries would look the same). In the config your posted, it seems like Caddy is redirecting through itself.