Shower screen, the thing that spreads water over the coffee bed in an espresso machine. It makes it so that the water wets the coffee roughly evenly instead of at a single spot. This helps with even extraction. The left is a diffusor the right is the shower screen. The diffusor has the same function but it does rough water distribution to six points in this case. The shower screen spreads it further.
Where did you dig up this ancient post from… 😄
But yeah things aren’t going spectacularly. A Kier Starmer scenario looks more likely at the moment.
They just stopped using a blade grinder recently.
Still being scrubbed. This residue is years old.
All-in, I wanted something on the order of 1MB for client app, server, all dependencies, everything.
Okay that’s gotta be radically different!
I was thinking along the same lines but then I thought about other neighbouring countries like Lebanon. Being recognized states didn’t stop Israel from doing whay they did to them. Not saying there’s no difference, I’m just not sure what the practical difference is. I’m probably ignorant.
Probably not.
Some hopium here.
Actively dismantling international law, I see.
Well, you gotta start it somehow. You could rely on compose’es built-in service management which will restart containers upon system reboot if they were started with -d, and have the right restart policy. But you still have to start those at least once. How’d you do that? Unless you plan to start it manually, you have to use some service startup mechanism. That leads us to systemd unit. I have to write a systemd unit to do docker compose up -d. But then I’m splitting the service lifecycle management to two systems. If I want to stop it, I no longer can do that via systemd. I have to go find where the compose file is and issue docker compose down. Not great. Instead I’d write a stop line in my systemd unit so I can start/stop from a single place. But wait 🫷 that’s kinda what I’m doing isn’t it? Except if I start it with docker compose up without -d, I don’t need a separate stop line and systemd can directly monitor the process. As a result I get logs in journald too, and I can use systemd’s restart policies. Having the service managed by systemd also means I can use aystemd dependencies such as fs mounts, network availability, you name it. It’s way more powerful than compose’s restart policy. Finally, I like to clean up any data I haven’t explicitly intended to persist across service restarts so that I don’t end up in a situation where I’m debugging an issue that manifests itself because of some persisted piece of data I’m completely unaware of.
Sorry, why do the bags have to be wet? Does the wetness affect the intelligence of a bag?
This has been a pretty educational moment ngl…
You said Trump bus originally. We were on the American bus, not the Trump bus. Once there was a change of driver to Trump, we got off at the next stop, as you pointed out.
Also most Canadians didn’t love PP either. Instead we were united in hating Trudeau, which is why the libs started climbing in the polls as soon as Trudeau left the room. Before there was a new leader.
These can’t shoot down F35, can they?
Let me know how the search performs once it’s done. Speed of search, subjective quality, etc.
Why start anew instead of forking or contributing to Jellyfin?
I think I lost neurons reading this. Other commenters in this thread had the resilience to explain what the problems with it are.
Recently learned that de-scaling a boiler exposes you to lead leaching from the brass walls till it acquires some scale. 🫠