ranjan@ranjan.info:~$ cat ~/.stack --verbose

The stack behind the work

Every technology below has run production workloads under my administration — not tutorial familiarity, but tools I've recovered, tuned, migrated, and been paged about. If your stack is on this page, I've probably fixed your problem before.

Operating Systems & Virtualization
Linux (AlmaLinux · Ubuntu · Debian)KVMLXCProxmoxVMwareVirtualizor
Web Servers & Edge
NginxApacheLiteSpeedReverse ProxyLoad BalancingCloudflareCDN
Hosting Platforms & Panels
cPanel · WHMDirectAdminPleskWHMCSCloudLinuxJetBackup
Databases & Caching
MySQLMariaDBRedisSQLiteInnoDB tuningReplication
Languages & Automation
BashPythonPHPGitREST APIssystemd
Containers & Cloud
DockerKubernetesAWSDigitalOceanHetznerCloud-init
ranjan@ranjan.info:~$ grep -c "production" ~/history

Depth, not logos

Three ways this list is different from a résumé keyword cloud.

Operated, not sampled

These tools ran commercial hosting under my name — thousands of servers' worth of updates, incidents, and 3 am pages.

Broken and repaired

Knowing a tool means having fixed it at its worst: corrupted tables, failed RAID, panel upgrades gone sideways.

Automated together

The real value is the glue — panels talking to billing, monitoring paging before customers, backups proving themselves nightly.

ranjan@ranjan.info:~$ which expert

Working with this stack?

Tell me which pieces you run and what hurts. If it's on this page, you'll get an answer grounded in years of production use — not a learning curve billed by the hour.