overview for klangcola

I just wanted to compare FOSS Linux budgeting software in c/mildlyinfuriating@lemmy.world

[–] klangcola@reddthat.com 2 points 4 days ago

The day after seeing this post I came across the exact same format searching for something unrelated on DuckDuckGo. The AI Sloppening is real

collapsed inline media

EU confirms it wants UK to pay into its budget in exchange for closer ties in c/europe@feddit.org

[–] klangcola@reddthat.com 9 points 4 days ago

Sounds a lot like EEA (Iceland Norway Lichtenstein)

Chat Control 2.0 has passed the first round of approval in c/europe@feddit.org

[–] klangcola@reddthat.com 4 points 1 week ago

It's not, unless you know the keys.

Keys are created by the software/app made by the service provider, like WhatsApp / Meta or Google. How is the key created, and is a copy sent back to WhatsApp? "Securely" and "No" they claim, and you just have to trust them.
That can change if WhatsApp need to comply with new laws.

Signal is a bit different because of the app is fully open source, so the code can be audited to verify the integrity of the encryption. They would still need to comply with laws or exit that market, but whatever they do would be 100% transparent.

Proxmox Backup Server: Bare Metal vs. Privileged LXC vs. VM? in c/selfhosted@lemmy.world

[–] klangcola@reddthat.com 2 points 1 week ago

I run PBS as a virtual machine on Proxmox, with a dedicated physical harddrive passed through to PBS for the data.

While this protects from software failures of my VMs, it does not protect from catastrophic hardware failure. In theory I should be able to take the dedicated harddrive out and put it in any other system running a fresh PBS, but I have not tested this.

I tried running the same PBS with an external NFS share, but had speed and stability issue, mainly due to the hardware of the NFS host. And I wasn't aware of autofs at the time, so the NFS share stayed disconnected

The Linux Kernel Looks To "Bite The Bullet" In Enabling Microsoft C Extensions in c/linux@programming.dev

[–] klangcola@reddthat.com 7 points 1 week ago (1 children)

In Danish and Norwegian the equivalent idiom is to "Swallow a camel" which sounds much funnier xD

*Permanently Deleted* in c/buyeuropean@feddit.uk

[–] klangcola@reddthat.com 24 points 2 weeks ago* (last edited 2 weeks ago)

SuSE is one of the two major enterprise Linux distributions, with RedHat being the other. I would assume servers make up the bulk of their business, but they provide desktops too.

RedHat is probably better known to most end-users, due to their Fedora community distribution, and their heavy involvement in Gnome.

SuSE's community distribution is openSUSE
EDIT: Fittingly, the very top of their website says "Make your old Windows 10 PC fast and secure again!" and links to https://endof10.org/

Bavaria wants to move to Microsoft cloud by year-end in c/europe@feddit.org

[–] klangcola@reddthat.com 16 points 2 weeks ago

Divide Germany you say? I feel like that's been done before

Germany lobbying China in interest of customers of Nexperia components in c/europe@feddit.org

[–] klangcola@reddthat.com 1 points 2 weeks ago

"Package" as in taking the raw chip and making it a finalised electronics component, as suggested here?

https://lemmy.world/comment/20348183

Netherlands' seizure of China chipmaker Nexperia sparks concerns among global auto companies in c/europe@feddit.org

[–] klangcola@reddthat.com 5 points 2 weeks ago (1 children)

Wow that makes so much sense!

When reading "packaging" in the news articles it sounds like some relatively simple logistics operating.

But for electronics and semi-conductors, the "packaging" is very much part of the manufacturing process to get a usable product. Like chips that come in Surface Mount and Through Hole versions

Microsoft Can't Keep EU Data Safe From US Authorities in c/europe@feddit.org

[–] klangcola@reddthat.com 4 points 2 weeks ago

This happened a while ago, article is from 22nd july

Euro cloud alliance urges action on Broadcom as Microsoft mends fences in c/buyeuropean@feddit.uk

[–] klangcola@reddthat.com 1 points 3 weeks ago

Yeah I agree there is good competition in that market these days, even if the transition work is costly. I'm sure a lot of companies are doing the math of paying the Broadcom VMWare tax Vs transitioning all their infrastructure

Euro cloud alliance urges action on Broadcom as Microsoft mends fences in c/buyeuropean@feddit.uk

[–] klangcola@reddthat.com 4 points 3 weeks ago (2 children)

But Broadcom does do software now, they bought VMWare in 2023, and implemented aggressive license changes. From the article:

Broadcom's acquisition of VMware and the subsequent price hikes haven't gone down well with all customers, to the point that many have been considering alternatives. Thierry Carrez, general manager of the foundation behind one such alternative, OpenStack, told The Register: "Broadcom's handling of VMware is a good example of the risk of trusting your infrastructure software fate to a single vendor. Those companies can be bought, can change direction, can change licensing terms anytime they want."

"Broadcom continues to tighten the screws on Europe's cloud infrastructure sector," said CISPE.

2

Why use Named volume vs Anonymous volume in Docker? (reddthat.com)

submitted 9 months ago by klangcola@reddthat.com to c/selfhosted@lemmy.world

3 comments fedilink

What are the pros and cons of using Named vs Anonymous volumes in Docker for self-hosting?

I've always used "regular" Anonymous volumes, and that's what is usually in official docker-compose.yml examples for various apps:

volumes:
  - ./myAppDataFolder:/data

where myAppDataFolder/ is in the same folder as the docker-compose.yml file.

As a self-hoster I find this neat and tidy; my docker folder has a subfolder for each app. Each app folder has a docker-compose.yml, .env and one or more data-folders. I version-control the compose files, and back up the data folders.

However some apps have docker-compose.yml examples using named volumes:

services:
  mealie:
    volumes:
      - mealie-data:/app/data/
volumes:
  mealie-data:

I had to google documentation https://docs.docker.com/engine/storage/volumes/ to find that the volume is actually called mealie_mealie-data

$ docker volume ls
DRIVER    VOLUME NAME
...
local     mealie_mealie-data

and it is stored in /var/lib/docker/volumes/mealie_mealie-data/_data

$ docker volume inspect mealie_mealie-data
...
  "Mountpoint": "/var/lib/docker/volumes/mealie_mealie-data/_data",
...

I tried googling the why of named volumes, but most answers were talking about things that sounded very enterprise'y, docker swarms, and how all state information should be stored in "the database" so you shouldnt need to ever touch the actual files backing the volume for any container.

So to summarize: Named volumes, why? Or why not? What are your preferences? Given the context that we are self-hosting, and not running huge enterprise clusters.