Is the CI/CD still a faithful clone of github’s worst-in-show setup? Because if I had a plan for ditching GL, the CI keeps forgejo from being a contender.

There is a community edition but serious users will run into its limitations

No true Scot, then?

I’m running gitlab implementations at a few sites. I’ve not seen or heard of any performance limiter with a self-managed community edition that removes a tool the others still provide.

and it does not integrate neatly with external solutions.

Again, this sounds FUDdy. Which ‘external solutions’ are you using that a git-push fails on? Some spaghetti of saas tendrils seems to be already a risk, but I can’t think of any other external thing that it could mess up with.

made due

made do?

everytime

Not a word yet. It may never be a word.

I wrapped the trade-offs here https://cxgo.ai/l/pti2J6s

The link goes to some wall of articles, none of them obviously about immich. Is there a better link?

Doood. npm in production is a bad pattern in this age of supply-chain sploits. Best vendor that into the artifact when ya ship … Nevermind.

(See: iso27002, SLSA.dev)

Container-free yet? #slsa.dev

outside of the ask

More outside of the question.

Are you connecting to the victim to push a backup into storage? If so, there’s SO much you should improve on that.

a software

‘Software’ is not a word that get an ‘a’ article. So

I was hoping there exists software that

or

I was hoping there exists a software package that

Having said that, you can install UltraVNC and have it ‘call home’; and it works very well.

Edit: Wow. So many people hate UVNC.

Still hosting gitlab.

The CI on forgejo is, unfortunately, nowhere near as good.

Given how long gitlab has been struggling to fix basic bugs and instead creeping into features - hello-oo bloated and slow vscode-like web editor and non-ephemeral runner management - I’m not sure they have any staff left to let go. But it’s nice they found an excuse to shed their remaining talent and avoid complete stock devaluation.

The planning is happening openly, including a voluntary separation window.

“We don’t understand how the Dead Sea Effect works, and we want to super-size the damage.”. Okay, Bill.

This should be a note on the sidebar of all ask-* subs.

Wow. I had to stop reading this one. Long on words, poor on writing and spelling and neither circling a theme so much as just edgelording on everything social, I’m not sure whether it was ever getting somewhere.

But life’s too short for 6000 words on The Things That Suck With Stuff I Don’t Use.

I shudder to imagine what they’d think of a car with a clutch and a left-toe switch for the high-beams.

• node.js
• mariadb server
• redis

You’ve got suppy-chain attacks and boutique complexity in three easy steps. Squeeze it into a flatpak or crutch on containers to frustrate validation and it’s the perfect footgun from a security standpoint.

Why be misunderstood from human reading comprehension when we can be misunderstood from sloppy reading comprehension? Yay for technology!

Heh. Container mafia going “hush, don’t worry about iso27002, just one more pull, bro.”

Do the sysctl fix and you’re fine to wait for a patch.

Disable the sandbox bit and it’s bobbitted, right ?

I’d like to host micro-instances for 1-2 subs for software: XYZApp-news and XYZApp-help or so, on the equivalent of a spur or leaf node.

But aPub seems to need M:M comms and so it needs to be out in the world instead of hidden behind an aPub proxy. True?