prettybunnys

Blending it is pre-digesting it which means it doesn’t travel our bodies quite the same way.

We have long digestive systems for a reason.

I’m not saying it isn’t possible but you’d probably shit funny for a long time

Did he deserve to die … idk, a good guy with a gun thought so?

No, but I hope he burns in hell too.

http://9front.org/

well, modern web browser probably fails the task but … it can be done.

Now that you’ve set zsh as default … switch to fish

Their

Weird, that page is likely for legacy customers as snowflake owns them and they’re now known by another name.

The logo itself they’re using is an old logo, predating 2022 when they moved to the “friendly hippo” away from “murder hippo”

Their sponsors list is pretty out of date, I clocked crunchydata on there which is now snowflake, and that’s an old logo

Flux the repo

It’s kinda weird for the mom and daughter, but not weird for the guy.

It’s easy to understand.

With constrained data sets it’s actually really useful.

Parsing text and logs and correlating events, super useful.

When you dump all human “intelligence” into it you discover how dumb we are collectively.

exactly, they were always green, but since the world was black and white some of them went cheap and put up a black board instead of the proper green.

When the world switched to color the black ones often were repainted.

Their move to attempt to monetize our on-prem runners might be the kick needed to move to Gitlab 🤞

Jenkins is better than many but IMO Gitlab pipelines are top tier.

Jenkins is good enough to be widely used enough to be hated enough to be downvoted.

The sign of a mature product IMO.

You could do worse than Jenkins

What issue do you have with using yaml to define a job?

docker inspect --format='{{json .State.Health}}' <container_name>

HEALTHCHECK is part of the Dockerfile syntax and ought to be supported by all your container runtimes

https://docs.docker.com/reference/dockerfile/#healthcheck

You could extend all the dockerfiles that don’t have a health check to implement this feature with whatever health check makes sense for the application, even if for now it’s just a curl of an endpoint.

What I am saying is that it looks significantly more daunting then it truly is, once you understand the basic concept of it (which I’m positing is actually fairly simple) the rest follows easily.

Specifically here though I mean SELinux is “simple” if you understand how Linux works and operates, as you’re constraining syscalls and access

SELinux is super simple, you just gotta understand how the system works.

Once you understand the syntax and flow of SELinux policy then writing it is easy. Writing GOOD policy on the other hand …. Lmao.

Typically most IT departments “fix” it with setenforce 0 which is the equivalent of removing the seatbelt cuz you can’t figure out how to latch it.

Android has one of the most “robust” applications of it but it doesn’t serve the purpose a good policy does, it does add a substantial layer of defense. Apple contracted my company to come out and teach them how to SELinux a few years back. Ultimately they (companies that desire SELinux as an added layer of defense) tend to just pay “us” to do it instead lmao.

Amazon throws money at people with niche skill sets.

They were paying engineers with experience with SELinux and CDS developers nearly 500k the past few years.

Insanity

When you say you’re using systems to lock down/containerize things as necessary can you explain what you mean?