This is generally done when you have customers with SSO, the first one will take the email and if the domain is ssod it forces them through a particular workflow. Otherwise you get the other normal username/password flow
I've found that people who talk about "code smell" generally should not be listened to as it's entirely vibes-based-on-the-last-medium-post-i-read-this-morning. I had a dipshit manager tell me that he didn't like my use of decorators (in python mind you) because it was a "code smell" and recommended I read "clean" code, and I immediately threw every other opinion he had in the trash.
As someone who spent countless hours of my youth in hammer, laying out areas with props and lighting and doing play testing about areal movement with test npcs, it's hilarious that these people see this slop and say, yes this is the future.
also : "I’m working on a theory that “AI is art” boosters have some kind of limited ability to perceive details. Like they literally only perceive large shapes, colors, and noises. Anything remotely more detailed than ‘big thing go boom’ they actually lack the ability to see it." 🤔🤔🤔
also: after discussing with my brother I came to the realization that this rube was likely very into the "play2earn" bullshit during the nft era
fyi: some fellow forked all of the sentry stuff from when it was bsd and made it less shit to run yourself. I'd been running sentry as self hosted since it came out effectively and they made some real questionable outright bad architecture decisions over the years that made running sentry super annoying to get you to use the saas product. Like yes I want to use Cassandra and elastic search for my one user error logging
So this is literally a rehash of Spyce, a CambridgeMA based startup whos first restaurant was in the old chipotle in harvard square. They had a similar setup but one that was able to make actually-hot food instead of salad bowls which were decent. (they ironically sold to sweetgreen in 2021)
I can speak for the tangara, lovely hardware but it is an mp3 player first and foremost. the hardware is technically capable of network stuff but their software stack is mostly focused on recreating that iPod experience and keeping the battery life to days of playback. It does take some getting used to if you've been living in musical algoworld for a minute
Your phrasing of the question implies a poor understanding. There's nothing preventing you from running containers on bare metal.
My colo setup is a mix of classical and podman systemd units running on bare metal, combined with a little nginx for the domain and tls termination.
I think you're actually asking why folks would use bare metal instead of cloud and here's the truth. You're paying for that resiliency even if you don't need it which means that renting the cloud stuff is incredibly expensive. Most people can probably get away with a$10 vps, but the aws meme of needing 5 app servers, an rds and a load balancer to run WordPress has rotted people. My server that I paid a few grand for on eBay would cost me about as much monthly to rent from aws. I've stuffed it full of flash with enough redundancy to lose half of it before going into colo for replacement. I paid a bit upfront but I am set on capacity for another half decade plus, my costs are otherwise fixed.
The way I've been using it for a few years is that most of my machines can see each other and I have a shared folder and versioning setup. As I add things they move between the different machines and once an additional machine has it it is available to the others until everything is in sync
You can definitely do chain topologies which are useful for certain things with a single source of truth
TIOBE merely measures the number of questions asked about a particular language online, which is obviously not exactly realistic metric but people for some reason love to spout it
As a note, I believe that syncthing will actually scale up with more nodes as they will all share with each other if they know each other. If you're doing this 1 to many then this is not the case of course.
Ive actually been personally moving away from kubernetes for this kind of deployment and I am a big fan of using ansible to deploy containers using podman systemd units, you have a series of systemd .container files like the one below
[Unit]
Description=Loki
[Container]
Image=docker.io/grafana/loki:3.4.1
# Use volume and network defined below
Volume=/mnt/loki-config:/mnt/config
Volume=loki-tmp:/tmp/loki
PublishPort=3100:3100
AutoUpdate=registry
[Service]
Restart=always
TimeoutStartSec=900
[Install]
# Start by default on boot
WantedBy=multi-user.target default.target
You use ansible to write these into your /etc/containers/systemd/ folder. Example the file above gets written as /etc/containers/systemd/loki.container.
Your ansible script will then call systemctl daemon-reload and then you can systemctl start loki to finish the example
This is generally done when you have customers with SSO, the first one will take the email and if the domain is ssod it forces them through a particular workflow. Otherwise you get the other normal username/password flow