That’s the neat part: they don’t!

Like, Nextcloud runs background tasks as a cron job which is something I’ve never seen with other hosted services.

Drupal also uses crons to run repeated tasks. By default, Drupal cron cleans out stale database records for a few tables and breaks old caches. It can be extended by the developer, though.

It’s probably a holdover from before containerised applications were ubiquitous but honestly it comes off as jank.

PHP is pre-container and pre-virtualization, so I guess you can think of it as a hack way of getting garbage collection. To be honest, the cron’s translate pretty well to k8s cronjobs. You just use the same image as the app and override the command with the cronjob command.

We will have so much winning […] that you may get bored with the winning. Believe me, I agree, you’ll never get bored with winning.

One of them post birth ones?

You got your laptop from Tim Apple, right?

May dragon mommy Astilabor bless them with wealth.

You should have replied, “I thought he was hanged on January 6th.”

Robbing hood

Yeah. Since he was a subcontractor, he wanted all his scripts to be the same, no matter who the customer was.

I was like jesus christ, I’m lazy too and want to automate everything, but edit your stupid scripts to use env vars.

We resolved it by making him use pipeline vars for his scripts. Like we told him to do in the beginning.

He fought it because he wanted his scripts the same for all projects. Including hard coded usernames and passwords. So, it was mostly his fault.

The production database gets down-synced to the lower environments on demand, so they can test on actual production datasets. That would require us to manually remake this user account every time a dev down-syncs the database to a lower environment.

The customer is paranoid, as the project is their public facing website, so they want testing against the actual prod environment.

We don’t mange the SSO, as that is controlled by the customer. The only local (application specific) account is this account for testing.

He had to do admin functionality regression tests before prod releases to make sure nothing broke.

The system uses SSO for logins for everything else.

He is a subcontractor who was using scripts for all his projects. I told him he really needs to use env vars for creds.

He was a subcontractor, so technically, he’s not our employee.

I bubbled it up the chain on our side, and it hasn’t happened since.

It was an admin account to do regression testing for the admin interface and functions before prod releases.

I had my guys enable/disable the account during the testing pipeline so people can’t login anymore.

deleted by creator

To be fair, spies like Maria Butina weren’t even that attractive. She was pretty mid, but had all the NRA guys simping.

I only use butterfly flaps that move magnetic needles next to my HDD.

I had a test engineer demand an admin password be admin/admin in production. I said absolutely not and had one of my team members change it to a 64-character password generated in a password manager. Dumbass immediately logs in and changes it to admin again. We found out when part of the pipeline broke.

So, we generated another new one, and he immediately changed it back to admin again. We were waiting for it the second time and immediately called him out on the next stand-up. He said he needs it to be admin so he doesn’t have to change his scripts. picard_facepalm.jpg

I have my instance running in my k3s cluster. I have its node affinity to only run on my minisforum i9. That way, I can use cert manager to manage the certs.

Why don’t you wear a suit? You’re at the highest level of this country’s office, and you refuse to wear a suit? I just want to see, do you own a suit?