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/)MG
Posts
16
Comments
399
Joined
4 mo. ago

  • I am using a reverse proxy in production. I just didn't mention it here.

    I'd have to set up a DNS record for both. I'd also have to create and rotate certs for both.

    We use LVM, I simply mounted a volume for /usr/share/elasticsearch. The VMWare team will handle the underlying storage.

    I agree with manually dealing with the repo. I dont think I'd set up unattended upgrades for my k8s cluster either so that's moot. Downtime is not a big deal: this is not external and I've got 5 nodes. I guess if I didn't use Ansible it would be a bit more legwork but that's about it.

    Overall I think we missed each other here.

  • The very act of writing FOSS code is altruistic. Indeed, I'm looking at the big corporations when I point and say "thief!".

    Some companies do work that I like though. Mullvad is a prime example. Recently I've been looking at Nym and I like their ideas and work. I really liked that the big giants like Google and IBM collaborated for k8s. I believe Uber has done something wonderful for the FOSS community too but I don't remember what it is. The fact is that they can if they try

  • Look, I understand if your boss tells you to not write Open-source/only use MIT so they can profit off of it later on. But for the people who have a choice, why wouldn't they? I don't see how it hurts their bottom line.

    I'm middle class and here I am raging on Lemmy about software licenses LMAO

  • Sorry, I'm not much of a software dev so bear with me:

    If the libraries are GPL licensed, is there a problem? Unless you're editing the libraries themselves.

    Now if the application is GPL licensed and you're adding functionality to use other libraries, please push upstream. It helps the community and the author will more likely than not be happy to receive it

  • By more moving parts I mean:

    Running ElasticSearch on RHEL:

    • add repo and dnf install elasticsearch.
    • check SELinux
    • write config
    • firewall-cmd to open ports.

    In k8s:

    • grab elasticsearch container image
    • edit variables in manifest (we use helm)
    • depending on if the automatically configured SVC is good, leave it alone or edit it.
    • write the VS and gateway (we use Istio)
    • firewall-cmd to open ports

    Maybe it's just me but I find option 1 easier. Maybe I'm just lazy. That's probably the overarching reason lol

  • I have and I've been left scratching my head both times. AppArmour just deals with files whilst SELinux has contexts - that's the only operational difference I've needed to notice. I create custom policies and am on my way.

  • Exactly. I use setroubleshoot myself and it's awesome.

    I agree that creating custom policies for a bunch of apps day in day out will be tiring. But that is an argument against all MAC. I personally don't want to see Linux going the way of abandoning MAC