Sure, but what you are describing is the problem that k8s solves.
I've run plenty of production things from docker compose. Auto scaling hasn't been a requirement, and HA was built into the application (so 2 separate VMs running the compose stack). Docker was perfect for it, and k8s would've been a sledgehammer.
towerful
joined 1 year ago
Any older disk based console also required a memory card.
Pretty sure the controller was the first to have an analogue joystick.
I think a lot of the quirks of the N64 were because they were essentially first drafts. A lot of first, a lot of ground breaking tech.
Nobody knew what they were doing, at that time: nothing was wrong
It's not a workaround.
In the old days, if you had 2 services that were hard coded to use the same network port, you would need virtualization or a different server and make sure the networking for those is correct.
Network ports allow multiple services to use the same network adapter as a port is like a "sub" address.
Docker being able to remap host network ports to containers ports is a huge feature.
If a container doesn't need to be accessed outside of the docker network, you don't need to expose the port.
The only way to have multiple services on the same port is to use either a load balancer (for multiple instances of the same service) or an application-aware reverse proxy (like nginx, haproxy, caddy etc for web things, I'm sure there are other application-aware reverse proxies).
Be the change. Make a dockerfile for it.
Follow the kbin install instructions, but convert them to dockerfile syntax.
Build it and push to docker.io or ghcr.io or whatever flavour you want.
Its a great learning experience, and containerisation is a huge part of the future (and present)
Getting a blowjob wasn't the crime. Lying under oath was the crime.
Same with this. The sex and hush money isn't a crime, it's the false business records that are
It's not a 10s soindbite, nor a 144 character tweet.
Of course he has no idea what is going on
"broker" as a service-between-services is a great name
It's sad. Also, not really surprising. KSP2 has had a very rough development cycle, and a very rough release.
Do they still support KSP?
No idea. Probably cause it's a bit gate-keepy in the way I say "any tuner worth their salt" as if it's the only way to achieve good results.
I haven't met a tuner that uses anything other than forks. Maybe that's because all the pianos I've worked with have been in good condition, so haven't needed drastic measures applied. As I haven't met a tuner that uses anything else, I can't say if they are better/faster/whatever. I just assumed it's the industry standard, like how orchestras tune by ear
I haven't, but I've had many grand and baby grand pianos tuned after being moved onto stage, and a guy comes in and does it by ear.
I asked them why they didn't have a stroboscopic tuner or something, and they've always found it easier with a couple forks and by ear
Im 99% sure any piano tuner worth their salt tunes by ear
Maybe tidal?
Tidal is basically Spotify, but cheaper, pays more to the artists and is, imo, better.
Googling for "tidal wearos" has some interesting bits, but I don't have a smart watch so I have no idea what I'm looking at