Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K

kumi

@ kumi @feddit.online

Posts
3
Comments
108
Joined
7 mo. ago

  • Do you backup your docker images?

    Jump

  • Just a small number of base images (ubuntu:, alpine:, debian:) are routinely synced, and anything else is built in CI from Containerfiles. Those are backed up. So as long as backups are intact can recover from loss of the image store even without internet.

    I also have a two-tier container image storage anyway which gives redundancfor the built images but thats more of a side-effect of workarounds.. Anyway, the "source of truth" docker-registry which is pushed to is only exposed internally to the one who needs to do authenticated push, and to the second layer of pull-through caches which the internal servers actually pull from. So backups aside, images that are in active use already at least three copies (push-registry, pull-registry, and whoevers running it). The mirrored public images are a separate chain alltogether.

    This has been running for a while so all handwired from component services. A dedicated Forgejo deployment looks like it could serve for a large part of above in one package today. Plus it conveniently syncs external git dependencies.

  • Rebranding our open-source Selfhosted social project to Bitsocial

    Jump

  • If not for political reasons then why limit first version to Google/GitHub rather than starting with generic OIDC (which should include those two anyway)?

    We also took your feedback seriously and we are now implementing proper sign-in options like: Google GitHub (and more coming later)

  • I made my home lab immutable with Terraform | XDA

    Jump

  • Sounds like you have a stable life and infra needs and either very lucky or really good with backups and keeping secondaries around. Good on you.

  • I made my home lab immutable with Terraform | XDA

    Jump

  • The advantage to using something like terraform is repeatability, reliability across environments and roll-backs.

    Very valuable things for a stress-free life, especially if this is for more than just entertainment and gimmicks.

    I'd rather stare at the terminal screen for many hours of my choosing than suddenly having to do it at a bad time for one.. 2... 3... (oh god damn the networking was relying on having changed that weird undocumented parameter i forgot about years ago wasnt it) hours. Oh, and a 0-day just dropped for that service you're running running on the net. That you built from source (or worse, got from an upstream that is now mia). Better upgrade fast and reboot for that new kern.. She won't boot again. The bootdrive really had to crap out right now didn't it? Do we install everything from scratch, start Frankensteining or just bring out the scotch at this point?

    Also been at this for a while. I never regretted putting anything as infra-as-code or config management. Plenty of times I wish I had. But yeah, complexity can be insiduous. Going for High Availability and container cluster service mesh across the board was probably a mistake on the other hand...

  • How do I make the Wordpress media library be somewhere else?

    Jump

  • NFS works great for media files and stuff but be careful and know what you are doing before you go put database storage on it.

  • DistroWatch Weekly - The new Chimera Linux installer

    Jump

  • Chimera Linux is very interesting. Has anyone here tried running it?

  • Help getting started with self hosting Jellyfin via NAS?

    Jump

  • One way to go about the network security aspect:

    Make a separate LAN(optionally: VLAN) for your internals of hosted services. Separate from the one you use to access internet and use with your main computer. At start this LAN will probably only have two machines (three if you bring the NAS into the picture separately from JF)

    • The server running Jellyfin. Not connected to your main network or internet.
    • A "bastion host" which has at least two network interfaces: One connected outwards and one inwards. This is not a router (no IP forwarding) and should be separate from your main router. This is the bridge. Here you can run (optional) VPN gateway, SSH server. And also an HTTP reverse proxy to expose Jellyfin to outside world. If you have things on the inside that need to reach out (like package updates) you can have an HTTP forward proxy for that.

    When it's just two machines you can connect them directly with LAN cable, when you have more you add a cheap network switch.

    If you don't have enough hardware to split machines up like this you can do similar things with VMs on one box but that's a lot of extra complexity for beginners and you probably have enough of new things to familiarize yourself with as it is. Separating physically instead of virtually is a lot simpler to understand and also more secure.

    I recommend firewalld for system firewall.

  • X.Org Server May Create A New Selective Git Branch With Hopes Of A New Release This Year

    Jump

  • Linux Snap Users Warned as Attackers Push Malware Through Old Trusted Apps

    Jump

  • Everything in there is relevant and applies to flatpaks too. Being aware of the risks is important when using alternative distribution methods. With power, responsibility.

  • Linux Snap Users Warned as Attackers Push Malware Through Old Trusted Apps

    Jump

  • Tricking users into using Snap without realizing it, making them unknowingly vulnerable to exploits like this, would be really really bad and unethical on Canonical’s part.

    That is not what is happening at all.

    Just so nobody is confused or gets afraid of their install: Getting the Firefox snap installed via Ubuntus apt package does not make users vulnerable to what is talked about here and is just as safe as the apt package version. For Firefox snaps might even be safer since you will probably get security patches earlier than with apt upgrades and get some sandboxing. In both cases you are pulling signed binaries from Canonical servers.

    The post is about third-party fake snaps. If you run a snap install command from a random web site or LLM wkthout checking it, or making a typo, then you are at risk. If Ubuntu didnt have snaps, this would be malicious flatpaks. If Ubuntu didnt have flatpaks, it would be malicious PPAs. And so on. Whatever hosted resource gets widely popular and allows users to blindly run and install software from third-parties will be abused for malware, phishing, typosquatting and so on. This is not the fault of the host. You can have access to all the apps out there you may ever want or you can safely install all your apps from one trusted source. But it's an illusion that you can never have both.

    People have opinions about if snaps are a good idea or not and thats fine but there shouldnt be FUD. If you are using Canonicals official snaps and are happy with them you dont have to switch.

  • I built LinuxMate to kill post-install chaos (free repo + demo)

    Jump

  • I do not ask you to read?

    So that's the mistake I made and the important part. Thanks for clarifying.

    I still feel misled that it's labelled as somehing it isn't ("my reasoning").

  • I built LinuxMate to kill post-install chaos (free repo + demo)

    Jump

  • It is indeed with the help of llm. But reasoning is still solid and very curated.

    It isn't your reasoning and promoting it as such when asking us to read doesn't feel honest at all.

  • Lemmy <> Nginx proxy manager nightmares

    Jump

  • Try answering the questions I asked for yourself and see if anything comes up!

  • I built LinuxMate to kill post-install chaos (free repo + demo)

    Jump

  • Linux MATE desktop is pretty established and I think has a similar audience. Pretty confusing name choice... "want to install mate on linux? Try linuxmate (no relation)"

    BTW are those actually your reasonings on the blog as you say? It reads very LLMy.

  • Lemmy <> Nginx proxy manager nightmares

    Jump

  • What makes you suspect the Nginx config instead of Lemmy? Do you have any failing requests (timeout or statuscode >= 400) in nginx log? What are the failing endpoints?

  • EDIT: BentoPDF version 1.16.1 now uses bentopdfteam/bentopdf and is the official account, and bentopdf/bentopdf is deprecated and not maintained anymore

    Jump

  • Both can be true.

    I think such character assessment and calling names is unnecessary and off-topic here though. Better engage with substance than judging by vibes and doing ad-hominem.

  • EDIT: BentoPDF version 1.16.1 now uses bentopdfteam/bentopdf and is the official account, and bentopdf/bentopdf is deprecated and not maintained anymore

    Jump

  • EDIT: BentoPDF version 1.16.1 now uses bentopdfteam/bentopdf and is the official account, and bentopdf/bentopdf is deprecated and not maintained anymore

    Jump

  • I guess they now have large enough number of users that it would be wise to shift some focus to supply-chain security from growth-hacking.

    This is growing pains.

  • I made a self-hostable frontend for instagram.

    Jump

  • Cool! Keeping up with platform changes is a challenge for projects like this. I think to be successful beyond initial popularity you need an active community that can do this together. It's draining for just one person - especially once you get big enough that they might actively break things just to mess with your integration. Following maintenance of alternative YouTube clients as well as searx-ng is illustrative.

    Not to discourage but be prepared. Best of luck!

    https://cadence.moe/blog/2022-09-01-discontinuing-bibliogram

  • Linux @programming.dev
    kumi @feddit.online

    Keeping persistent history in bash

    eli.thegreenplace.net /2013/06/11/keeping-persistent-history-in-bash
  • Linux @programming.dev
    kumi @feddit.online

    Dealing with faulty RAM modules in 2026

    blog.kumio.org /posts/2026/01/memtest86plus.html
  • Selfhosted @lemmy.world
    kumi @feddit.online

    Dealing with faulty RAM modules in 2026

    blog.kumio.org /posts/2026/01/memtest86plus.html