klangcola

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

There's strong Farquaad vibes here..

Some of you may die, but that's a sacrifice I'm willing to make

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

Huge, but full of rocks and mountains and fjords. "Arrable land" is at a premium. Norwegian farmers look at danish and Dutch fields with much envy

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

Especially with all the work being put in to Forgejo CI/CD lately

[–] klangcola@reddthat.com 8 points 1 month ago (1 children)

Good catch, that licence does not look very Libre =\

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

Paywalled, so can't comment on the whole article.

But the excerpt does not support the headline: Share of EU GDP says nothing about internal or external trade growing or shrinking, only that the relative amount of external to internal trade move to slightly more external

[–] klangcola@reddthat.com 12 points 2 months ago (6 children)

Not sure I buy the "not critical infrastructure" argument. Even if 95% of public (and private) correspondence is digital these days, paper-mail is still used as a fallback for some institutions and whenever a physical copy must be sent for whatever reason.

[–] klangcola@reddthat.com 2 points 3 months ago

Yikes, are those required? Looks very rug-shaped, perfect for pulling things. Or not. Who knows?

[–] klangcola@reddthat.com 3 points 3 months ago

Yeah it's a normal model, but BitWarden is a bit special in that their original server-side implementation was enough of a pain to self-host on a small scale that an alternative implementation Vautlwarden was created. And Vaultwarden became very popular in self-hosted circles. And now many years later BitWarden offers a Lite server which scales down. I think it's a good thing, just a bit unusual. I'm struggling to think of similar examples.

I'm sure Vaultwarden still funnels plenty of enterprise use of BitWarden, since Vaultwarden users still use official BitWarden client.

[–] klangcola@reddthat.com 10 points 3 months ago

Forward thinking venture capital funded companies are getting rarer, hence the question on motivation. Especially the last few years many VC Foss companies have squeezed harder the other way (gitea, Terraform, docker). So all kudos to BitWarden for launching Lite.

What you say a about brand dominance, or brand protection makes a lot of sense. It's not a good look for them that a large number of people choose to use an unofficial implementation instead of theirs. And should there ever be a catastrophic security issue with Vaultwarden, it would still reflect bad on BitWarden as that kind of nuance (like "unofficial server side implementation") tend to get lost in reporting. Having more IT workers self-host official version probably also helps pave the way for bringing enterprise-bitwarden to companies.

Valve are a bit of a unicorn though, because they are privately owned. There's no investors demanding ROI the next quarter, which gives them freedom to think long term.
When Microsoft launched windows8 and the Microsoft Store, Valve took that as an existential threat to their whole business model (the Steam store). Valve feared that Microsoft was trying to position itself like Apple on iOS and Google on Android, where there is only one platform store, and all apps are purchased through the platform store, and the platform store takes that sweet sweet 30% cut. So Valve pivoted to ensure the Steam store would not be obsolete, and give customers a reason to still use the Steam store. And what they achieved is awesome, for Linux, for Valve and for gamers. But it took nearly a decade, which is a level of patience few companies have.

[–] klangcola@reddthat.com 56 points 3 months ago (11 children)

Wonder what's the reasoning behind offering this Lite version. I don't imagine competing with Vaultwarden is very lucrative financially.

[–] klangcola@reddthat.com 2 points 3 months ago

To be honest I don't remember why I set up gitea with MySQL instead of sqlite (or MariaDB), its quite a few years ago. And sqlite would probably be fine for my single-user instance

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

It's a bit of a sad state of Europes electric car manufacturering that the only two mentioned manufacturers are Volvo/Polestar, both wholly owned by Chinese Geely, with production in China.

The ChargeUp organisation consists of charging infrastructure providers (including gas station companies like CircleK, BP, Total). The only manufacturer is (American) Tesla, presumably because of their charging infrastructure division. https://www.chargeupeurope.eu/membership

EmobilityEurope organization is mostly driver-associations and supply chain companies. The actual manufacturers are:

  • Lucid (American)
  • GM (American)
  • Tesla (American)
  • Polestar (Chinese/Swedish)
  • NIO (Chinese)
  • Rivian (American)
  • Smart (initially German, currently Chinese)
  • Volvo (Chinese/Swedish)
    https://www.emobilityeurope.org/our-members/

So not a single European (electric) car manufacturer is involved

 

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.

view more: next ›