41–50 of 138 posts
I just went back to kind of "anonymous ftp" via my gemini site on sdf.org. I find it far easier to maintain. When I make a change, a script packages up the change and sends it to sdf. My github repositories were changed to point to it. The latest change by Microsoft made me move, I was considering a move when Copilot became a thing. 2FA got me off my butt to finally move.
What about requiring 2FA made you leave?
I’ve been moving into a self-hosted direction for a lot of my stuff as a lot of it really wasn’t being used by anyone but myself anyhow. My latest two projects are darcs on my home server using just SSH+Nginx for HTTP with an apply hook that run `nix flake check` & on the server end, a hook that runs `nix build` which not only checks the build, but also has the derivation in Nix store for me to pick up later as that…
EDIT: here's how I do it, in case it's useful: https://github.com/Misterio77/nix-config/blob/a74b2ede/hosts...
Having tried GitHub, GitLab, Source Hut, Codeberg, and BitBucket (RIP), I think the only serious options are GitHub, GitLab self hosted, and Source Hut. GitHub owned by MSFT aside, and also putting their AI push _also_ aside, GitHub has things like Sponsors, Dependabot, and code scanning that you won't find anywhere else. They sure are luring you into ecosystems that require a huge escape velocity, but GitHub serves…
Not a very serious option if you're looking for anyone from the 21st century to contribute to your project. No, the email workflow doesn't get better by just screaming "it's not that bad!" over and over again.
I'm looking forward to the federation work that is being done for forgejo, that will be big if it works out as it seems like it will.
> Rather than needing a complicated YAML file to run a CI system, it’s just cloning Git repos and running commands. How do you define what repos you need and which commands are run? Ah, it is indeed also a YAML file: https://srht.site/automating-deployments
But is it a _complicated_ YAML file?
> Rather than needing a complicated YAML file to run a CI system, it’s just cloning Git repos and running commands. How do you define what repos you need and which commands are run? Ah, it is indeed also a YAML file: https://srht.site/automating-deployments
But is it a _complicated_ YAML file?
That was definitely the most bullshit criticism in the article. Clearly not even something they actually care about because they settled on Drone CI which is configured in exactly the same way.
They don't like "AI-powered" because it is a vague, ill-defined term... except it's extremely obvious and well defined what GitHub means by that (and they've even used copilot and liked it!)
Gitlab CI is rejected because it uses YAML for config... like every other CI system they mention.
Gitlab isn't ok because it's open core, but Drone CI is.
Could have been an interesting comparison but it wasn't.
Earlier quoted context omitted.
Sad to see this down voted. I agree. They also sound insufferable. Maybe it's just their writing style, trying to be inflammatory for engagement, but they are not someone I would want to work with.
You and the parent seem to dislike the author sharing their opinions on things on their own blog . And yet you're happy to share your own dismissive opinions on the author here. FWIW I find the author's obviously subjective opinions on their tools much more valuable than your obviously subjective opinions of this author.
At least w.r.t. the original comment, this seems like a misunderstanding. GP was saying that, absent any explanation for why the author came to the opinions they did, the article doesn't say much of value. They don't dislike the author sharing their opinions on the author's own blog.