tvcvt

@tvcvt@lemmy.ml

• ⁨Comment⁩ on ⁨Self-hostee storage for Gmail⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  The thing that immediately came to mind was mailpiler.org. It’s been on my list to stand up for a while, but I’ve never got around to it.

• ⁨Comment⁩ on ⁨Proxmox: Trouble with permissions with a a mountpoint in a lxc "audiobookshelf"⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  Awesome. I’m glad it helps. I’d be a little weary of using the same directory in multiple containers. File systems may or may not behave well with multiple machines writing to them. Not saying anything bad will happen, but do keep an eye out for issues.

• ⁨Comment⁩ on ⁨Proxmox: Trouble with permissions with a a mountpoint in a lxc "audiobookshelf"⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  I’m making some assumptions, namely that you’re using an unprivileged LXC container and the mount point is a bind mount.

  Unprivileged LXC shift user ID numbers so that an escape won’t result in root access to the host. The root user (uid 0) in the container is actually uid 100000 from the perspective of the Proxmox host.

  What I usually do is set ownership of my bind mounts to that high-numbered ID (so something like chown -R 100000:100000 /path/to/bind/mount) from Proxmox. Then the root user in the container will be able to set whatever permissions you need directly.

• ⁨Comment⁩ on ⁨Homelab Organization⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

  Dokuwiki (dokuwiki.org) is my usual go-to. It’s really simple and stores entries in markdown files so you can get at them as plain text files in a pinch. Here’s a life lesson: don’t host your documentation in the machine you’re going to be breaking! Learned that the hard way once or twice.

  For reverse proxies, I’m a fan of HAProxy. It uses pretty straightforward config files and is incredibly robust.

• ⁨Comment⁩ on ⁨Docker email server to host mail archive⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

  I can’t give direct experience here, but this is exactly the use case I’ve been meaning to spin up mailpiler for: www.mailpiler.org. One of these days that will rise to the top of the priority list.

• ⁨Comment⁩ on ⁨Proxmox Disk Performance Problems⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  There was a recent conversation on the Practical ZFS discourse site about poor disk performance in Proxmox (discourse.practicalzfs.com/t/…/1421/). Not sure if you’re seeing the same thing, but it could be that your VMs are running into the same too-small volblocksize that PVE uses to make zvols for its Vans under ZFS.

  If that’s the case, the solution is pretty easy. In your PVE datacenter view, go to storage and create a new ZFS storage pool. Point it to the same zpool/dataset as the one you’ve already got and set the block size to something like 32k or 64k. Once you’ve done that, move the VM’s disk to that new storage pool.

  Like I said, not sure if you’re seeing the same issue, but it’s a simple thing to try.

• ⁨Comment⁩ on ⁨Good file servers for Proxmox⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  My go-to for this is a plain Debian or Ubuntu container with Cockpit and the 45Drives file sharing plugin. It’s pretty straightforward and works pretty well.

• ⁨Comment⁩ on ⁨Pause alerts during the night⁩ ⁨⁨7⁩ ⁨months⁩ ago⁩:

  You can set maintenance schedules in Uptime Kuma and alerts won’t be sent out during those times. I use that for when my backup routines run each night. That seems like a decent cross-platform work around.

• ⁨Comment⁩ on ⁨Restart Docker Container Without root privileges⁩ ⁨⁨7⁩ ⁨months⁩ ago⁩:

  Not sure how your stack works together, but sudo will let you run particular commands as a different user and you can be pretty specific with the privileges. For example you can have a script that’s only allowed to run docker compose -f /path/to/compose.yml restart containername as a user in the docker group. Maybe there’s some docker-specific approach, but this should work with traditional Unix tools and a little scripting.

• ⁨Comment⁩ on ⁨Podman won't start Pihole with an error saying that it can't bind to port 53, as it is already in use, but nothing is using port 53.⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  I’ve not done much with podman, but my first thought is that port 53 is privileged and usually podman runs as a non-privileged user, right? Do you have some mechanism in place that would allow podman to use port 53?

• ⁨Comment⁩ on ⁨Best Way To Mount A Directory on Boot⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  It sounds like you’ve got your solution already, but just in case someone stumbles on this later, I thought I’d mention autofs.

  I’m coming to prefer it over fstab entries because it handles disconnections nicely and attempts to reconnect. Worth checking out for those who haven’t played with it.