hamsda

@hamsda@feddit.org

• ⁨Comment⁩ on ⁨self-hosted KeePass database in the cloud, what are some good options?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Before I got more into selfhosting, I was running nothing but syncthing in a Raspberry Pi.

  The pi was the “Server” and all the other Clients were only connected to the pi (in syncthing).

  Worked flawlessly :)

• ⁨Comment⁩ on ⁨Do you stick to the same linux distro across your devices?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Ha, I wish I could.

  I’m not 100% satisfied, so I’m still searching for the “perfect distro for me”, if it even exists.

  I have been using Arch Linux on my personal PC and company laptop for 4 years, but I couldn’t get some things to work. Things that, after installing Fedora, worked out of the box.

  My current setup is:

  • EndeavourOS (e.g. arch linux with a GUI-installer) for my PC at home
  • Fedora Workstation 43 for my company laptop
  • Servers are all running Debian, I’ll probably never change that
  • Hypervisor for VMs is Proxmox VE, which is Debian too
• ⁨Comment⁩ on ⁨How to reach different services via name instead of ip?⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  Currently using nginx-proxy-manager for exactly this purpose. Nice and easy-to-use UI, including automatic LetsEncrypt ssl certificates :)

• ⁨Comment⁩ on ⁨Looking for FOSS server monitoring UI⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  I’m using CheckMK to monitor my hypervisor, physical hardware like disks, CPU etc. and SNMP-capable hardware like my pfSense firewall via a CheckMK instance in docker. It either works in docker or on a few different linux based OS like ubuntu and debian (see CheckMK download page).

  There’s a free and open source version (called raw edition, GitHub Link) which I am using. It comes with a lot of checks / plugins for monitoring stuff out of the box and if there’s something it doesn’t ship, you can easily create your own check in whatever language your server is capable of executing a binary of. Or you could look up if there’s a user-contributed plugin on the official CheckMK Exchange Platform.

  The whole configuration of this is based on rules with a lot of predefined rules and sane defaults already set.

  To have an example for your use-case: You can monitor docker-logfiles and let CheckMK warn you, if specific keywords are or are not in a logfile. You will then be able to view the offending lines in the monitoring UI.

  Why do I use this?

  • We use it at work
  • FOSS
  • docker makes updating this easy
  • can send mails, teams notifications, …
  • very customizable and expandable

  my docker compose file

  # docker-compose.yml
  
  services:
    monitoring:
      image: checkmk/check-mk-raw:2.4.0-latest
      container_name: monitoring
      restart: unless-stopped
      environment:
        - CMK_PASSWORD=changeme
      ports:
        # WEB UI port
        - "5000:5000"
        # agent communication port
        - "8000:8000"
        # used for SNMP
        - "162:162/udp"
        - "514:514/tcp"
        - "514:514/udp"
      volumes:
        - "./monitoring:/omd/sites"
        - /etc/localtime:/etc/localtime:ro
      env_file:
        - .env
  

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  To me it seems like:

  • you want to do a lot of stuff yourself on arch
  • but there’s quite some complicated stuff to learn and try

  I’d try Proxmox VE and, if you’re also searching for a Backup Server, Proxmox Backup Server.

  I recommend these because:

  • Proxmox VE is a Hypervisor, you can just spin up Arch Linux VMs for every task you need
  • Proxmox VE, as well as Proxmox BS are open source
  • you can buy a license for “stable updates” (you get the same updates, but delayed, to fix problems before they get to you)
  • includes snapshots, re-rolls, full-backups, a firewall (which you can turn on or off for every VM), …

  I personally run a Proxmox VE + Proxmox BS setup in 3 companies + my own homelab.

  It’s not magic, Proxmox VE is literally Debian 13 + qemu + kvm with a nice webui. So you know the tech is proven, it’s just now you also get an easy to use interface instead of virsh console commands or virt-manager.

  I personally like a stable infrastructure to test and run my important and experimental tuff upon. That’s why I’m going with this instead of managing even the hypervisor myself with Arch.