butitsnotme

@butitsnotme@lemmy.world

• ⁨Comment⁩ on ⁨What's a standalone open source project that does file searching?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  What about simply shelling out to ripgrep?

• ⁨Comment⁩ on ⁨Small VPN Access Device?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  These devices have been recommended in the past, and it looks like they can run OpenWRT

  www.amazon.com/…/B09N72FMH5

  openwrt.org/toh/gl.inet/start

• ⁨Comment⁩ on ⁨Why is Google takeout so bitchy?⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  I know it’s not ideal, but if you can afford it, you could rent a VPS in a cloud provider for a week or two, and do the download from Google Takeout on that, and then use sync or similar to copy the files to your own server.

• ⁨Comment⁩ on ⁨Help with deployment⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  For no 1, that shouldn’t be dind, the container would be controlling the host docker, wouldn’t it?

  If so, keep in mind that this is the same as giving root SSH access to the host machine.

  As far as security goes, anything that allows GitHub to cause your server to download (pull) and use a set of arbitrary of Docker images with arbitrary configuration is remote code execution. It doesn’t really matter what you to secure access to the machine, if someone compromises your GitHub account.

  I would probably set up SSH with a key dedicated to GitHub, specifically for deploying. If SSH is configured to only allow keys for access, it’s not much of a security risk to open it up to the internet. I would then configure that key to only be able to run a single command, which I would make a very simple bash script which runs git fetch, and then git verify-commit origin/main (or whatever branch you deploy), befor checking out the latest commit on that branch.

  You can sign commits fairly easily using SSH keys now, which combined with the above allows you to store your data on GitHub without having to trust them to have RCE on your host.

• ⁨Comment⁩ on ⁨How to detect problems on computer?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  If you’re seeing an OOM killer messsage note that it doesn’t necessarily kill the problem process, by default the kernel hands out memory upon requestt, regardless of whether it has ram to back the allocation. When a process then writes to the memory (at some later time) and the kernel determines that there is no physical ram to store that write, it then invokes OOM Killer. This then selects a process and kills it. MySQL (and MariaDB) use large quantities of ram for cache, and by default the kernel lies about how much is available, so they often end up using more than the system can handle.

  If you have many databases in containers, set memory limits for those containers, that should make all the databases play nicer together. Additionally , you may want to disable overcommit in the kernel, this will cause the kernel to return out of memory to a process attempting to allocate ram and stop lying about free ram to processes that ask, often greatly increasing stability.

• ⁨Comment⁩ on ⁨worth selfhosting immich or similar? what about backups?⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  I backup to a external hard disk that I keep in a fireproof and water resistant safe at home. Each service has its own LVM volume which I snapshot and then backup the snapshots with borg, all into one repository. The backup is triggered by a udev rule so it happens automatically when I plug the drive in; the backup script uses ntfy.sh (running locally) to let me know when it is finished so I can put the drive back in the safe. I can share the script later, if anyone is interested.

• ⁨Comment⁩ on ⁨Google Photos Alternative⁩ ⁨⁨10⁩ ⁨months⁩ ago⁩:

  It’s been added recently, in the form of External Libraries.

• ⁨Comment⁩ on ⁨Why and when should I use LVM?⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  I did not know that, last I looked it was still in development, I believe.

• ⁨Comment⁩ on ⁨Why and when should I use LVM?⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  Something that LVM supports but ZFS and BTRFS don’t, is the ability to reduce your storage. (That is, to empty and remove a drive from the array, without having to completely destroy the storage array.) As a home user without sufficient storage to have complete duplicates of everything, I find this an important feature.

• ⁨Comment⁩ on ⁨The iPhone 13 mini is dead, leaving small phone lovers in a lurch⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  In Settings -> Accessibility-> Touch -> Assistive Touch you can configure a small button the floats on the screen (you can move it around), providing access to all sort of gestures and functions one handed.