• 1 Post
  • 63 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • Self hosting is a great opportunity to learn about some popular technologies and even acquire a few sysadmin skills. Required knowledge of a self-hosted solutions tech stack is not gatekeeping any more than required knowledge of tools and building materials is gatekeeping when it comes to renovating your bathroom. In either scenario, if you don’t know what you’re doing, it’s going to be a much more difficult job.

    reverse proxies

    That said, you should not be exposing any of your services to the public if you don’t know what you’re doing. That’s a quick way to a bad time.





  • In this situation it’s not necessarily that it’s the “right” or “wrong” device. The better question is, “does it meet your needs?” There are pros and cons to running each service in its own VM. One of the cons is the overhead consumed by the VM OS. Sometimes that’s a necessary sacrifice.

    Some of the advantages of running a system like Proxmox are that it’s easily scalable and you’re not locked into specific hardware. If your current Beelink doesn’t prove to be enough, you can just add another one to the cluster or add a different host and Proxmox doesn’t care what it is.

    TLDR: it’s adequate until it’s not. When it’s not, it’s an easy fix.






  • I want to make sure I understand your goal correctly. Here’s what I’m getting.

    1. You have a wire guard connection that you want to use for outbound traffic from your local LAN.
    2. You have a Debian box that serves at the client in this situation.

    Here’s the part where I’m a little fuzzy

    1. You want to connect to your local LAN using another wire guard connection and have WAN requests routed from clients connecting to your LAN (via wire guard) out the wire guard connection mentioned in #1.

    Did I get any part of that wrong?

    Edit: NVM. I saw your response to another comment that sounds like this is exactly what you want.

    This should be achievable via routing. I actually do the same thing. The main difference is all the work is done on my router which handles both wire guard connections and routing.

    At the minimim you’re going to need:

    • A NAT rule on your local router to port forward incoming wire guard requests on the WAN to your Debian box. **Assuming the Debian box is also the wire guard server.
    • An iptables DSTNAT rule on your Debian box to route local traffic to the LAN gateway.
    • An iptables DSTNAT rule on your Debian box to route outbound WAN traffic that does NOT originate from your Debian box to the gateway at the other end of the outbound wire guard connection.


  • Personal finance software is tough. It’s costly to develop, even with a very limited feature set. Automatic transaction downloads are a must if you want widespread adoption and that has its own set of complications.

    I still use Quicken – which doesn’t get anyone excited since it’s still a Windows (and Mac) desktop app built on an ancient codebase – but I’m a power user and have yet to find an adequate replacement. It’s not sexy but it does the job. I’m more the exception than the rule. The average user probably doesn’t need or care about the same features that I do.

    Oddly enough, one of its redeeming qualities is that it runs quite well on Linux through Wine.



  • jubilationtcornpone@sh.itjust.workstoSelfhosted@lemmy.worldTape drive backups
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    5 months ago

    My advice is avoid tape backups. The cost, risk of media degredation, and management overhead make them not worth it, especially for a homelab.

    Also, restoring an entire VM is almost easier than recovering a single file, just because of the sequential nature of reading data from a tape. Data recoveries are pretty slow in general.

    I backup to an external hard drive with regular copies to iDrive S3. Been doing it that way for a number of years with no problems.