klangcola

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

I'm confused how they don't already? More than 3500kg gross weight capacity is no longer a class B "car" but a class C/C1 "truck" and require a C1 license

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

"Pumped storage" is already a thing. Using excess grid electricity to pump water uphill.

Though excavating underground cavern for pumped storage sounds exceedingly expensive:O

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

Hydro is definitely highly geography dependant, and certainly the environmental impact can be severe. Though there's also been great advancements in smaller scale "low head" hydro where you don't need to submerge half a valley or block migratory paths. Hence curiosity where hydro stacks up.

I suppose it's so geography dependant you can't make a meaningful global average to compare with other forms.

Then again in my particular neck of the woods solar is limited at best, for half the year. While the local landscape is nothing but mountains, valleys , lakes and rivers. So many lakes and rivers.

Another neat thing about hydro is that it's a renewable base load. Geothermal is another, but that's also highly geography dependant

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

Disappointing DW didn't include hydropower in the price comparison graphic. Also would have been interesting to see where offshore wind stacks up, though tbh I'm not sure the math is even in yet for offshore wind

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

My gut reaction too. But their readme/faq makes a lot of sound points. Also Nextcloud is one of the main contributors, so you know it's serious. Also Proton and Ionos (which I admit I'd never heard of, but they seem big)

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

You might be interested in an immutable distro. Like Bazzite or other Silverblue / Ublue flavoured system. They are recent but not bleeding edge, deploy well tested images that apply as all-or-nothing. Very stable, very featurful :)

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

You're basically calling bullshit on a charity having increased fuel prices, because you're not aware of any Iran conflict!

Perfect metaphor

[–] klangcola@reddthat.com 0 points 3 weeks ago (1 children)

Super aggressive scraping bots who ignore robots.txt

It's not unique to Gnome, and it's been a problem for a year or so

[–] klangcola@reddthat.com 11 points 3 weeks ago (13 children)

I imagine AI scrapers have a lot to do with the massively increased hosting costs. I'm assuming Anubis et al didnt fix all their bot traffic issues

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

Perfectly sound logic, I see no flaws with this argument

[–] klangcola@reddthat.com 22 points 1 month ago

Yes

Come to the dark side, we've got new Plasma, and exhausting manual configuration

[–] klangcola@reddthat.com 1 points 1 month ago

Thanks, I'll add VSCode/ium to the arsenal. I tend underutilize VSCode since Kate usually does everything needed by a text editor without all the baggage.

 

On windows, Notepad++ compare plugin let's you compare unsaved files. So to compare two texts copied from elsewhere, just make two new tabs and paste the texts. Compare plugin will happily compare line by line.

On Linux I havent found something similar. The closes is Kate, but you still have to save tmp1.txt and tmp2.txt , and remove the clutter when finished.

Does anybody know a compare app that just lets you paste two text blocks without saving files first?

 

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 ›