Przemysław Kołodziejczyk

So I'm torn: Forgejo feels better governance-wise, but Gitea feels more practical for my needs today.

#forgejo #gitea

Follow-up on #Forgejo vs #Gitea:

I read more about the split, and I'm still not sure.

I understand the governance concerns around Gitea, and Forgejo’s FOSS/community direction is very appealing.

But #Gitea supports #OpenTofu state, which I need, and I don't think "open source + paid hosting/support" is a bad model. Actually, it can be one of the healthier ways to fund development.

Maintainers should be paid. Good open-source tools need time, money, and boring long-term maintenance.

Self-hosted Git in 2026: Forgejo, Gitea or SourceHut?

I value open-source governance, but I also care about polish, UX, Actions, OpenTofu state, security, and long-term maintenance.

Which would you choose for a small/private team, and why?

#git #forgejo #gitea #sourcehut

Source: https://github.com/eshlox/dvm

macOS only. Small, inspectable, no daemon, no plugin runtime. Feedback and pull requests welcome.

#SupplyChainSecurity #npm #InfoSec #DevSecOps #macOS #Linux #Lima #Bash #Sandbox #AISecurity

I got tired of every dev tool, npm script, #AI agent, and random postinstall having full access to my Mac.

So I built DVM: tiny Bash + #Lima wrapper for disposable Fedora dev VMs.

One project. One #VM. Optional SSH/GPG keys. Dotfiles if you want. Burn it when done.

Keep your friends close, your supply chain in a VM.

https://github.com/eshlox/dvm

I found #lime-vm this week. It looks like a nice tool to make a separate #VM for each project on #macOS. Testing it now.

Still juggling .env files? I wrote up how I set up #Infisical for local #dev. The #CLI injects #secrets straight into your process so nothing ever hits disk, and the free tier is enough for small teams.

https://eshlox.net/setting-up-infisical-for-local-development

When a hacker breached #Vercel, they didn't need your #password. One employee's #OAuth token was enough. Host on a platform and you inherit their entire chain: every employee, every tool those employees use, every vendor behind those tools. Wrote about this.👇 Is a plain #VPS actually the safer setup, or is the platform risk worth the convenience? 🤔

https://eshlox.net/cloud-provider-attack-surface

Another day, another cloud #breach. As usual, a mini #server on my desk would be more #secure. (maybe a joke, maybe not)

#1Password is great for personal passwords, but its CLI falls apart for dev secrets: no project structure, prompt fatigue, all-or-nothing access. I moved to #Infisical. Do you know something better? Share it!

https://eshlox.net/why-1password-cli-fails-for-developers

Automatic #tmux window names with #just.

https://eshlox.net/tmux-window-names-with-just

#just: a simple command runner

https://eshlox.net/just-command-runner

Why I moved my workflow to the terminal.

https://eshlox.net/terminal-workflow

#helix #tmux #lazygit #just #terminal