Proof you need to thoroughly play test house rules before having a larger rollout.

Someone already did.

I was going to say you have to start use Alpine with the Pine email client. But IIRC, Pine stopped development, and a new project called Alpine took over.

So, now use Alpine to run Alpine and start calling it Alpine Linux Alpine Linux.

You wouldn’t understand. He’s playing 603D chess.

What are you talking about? The whole planet has been stuck in the Immaterium for the last decade.

Hey now! They could catch fire before the make it to a bridge.

The private school is the living room.

He*

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.

Make sure it has the right branding. Trumpflation.

He did say that all their offshore money will be untaxed, unlike the plebs.

Sailing the high seas

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.