Yes. I’m doing that with a 7040mff right now.

Mature software doesn’t need hourly updates. All the shit that leverages the library repos in horribly unsafe ways - ohai npm - that stuff needs constant updates.

The server part seems to be container-only. That’s a shame if you’re aware of iso27002 or SLSA.

The server side doesn’t seem to have a container-free install. I hope it works well for you but for me and mine it ceases to exist.

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)

Especially. Please tell me if wow voice chat works now under Experimental. It’s been hinky.

Container-free yet? #slsa.dev

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