Luca Cavallini

Server / DevOps

Linux server management for e-commerce

The machines under it all: cPanel/WHM, Proxmox, Debian/Ubuntu, KVM/LXC, database tuning, backups and monitoring. Built, secured, and kept running — not just deployed and forgotten.

Most developers stop at the code. I don’t — I’ve run the infrastructure under production shops for over fifteen years, and I lead operations for a hosting platform. That means I understand the part that actually keeps a business online: what happens at 2am when something breaks.

I build servers to be fast, secure and observable, and I keep them that way — backups that are tested, monitoring that warns you before customers do, and a person who answers when it matters. If you’d rather not think about your server, that’s the point.

Scope

What’s included

  • Setup & hardeningDebian/Ubuntu/CentOS, cPanel/WHM or Proxmox, KVM/LXC — provisioned, secured and documented.
  • Performance tuningPHP-FPM, MySQL/MariaDB, Redis, web server and OS tuned for real e-commerce load.
  • Backups that workAutomated, off-site, and actually restore-tested — not a cron job nobody ever verified.
  • Monitoring & alertingUptime, resources and services watched, so problems are caught early, not reported by users.
  • Security & updatesPatching, firewall, TLS, access control and incident response — kept current, not left to rot.
  • Migrations & scalingServer-to-server moves and capacity changes done cleanly, with minimal downtime.
FAQ

Questions, answered

Do you offer ongoing management or one-off work?
Both. Many clients keep me on a monthly arrangement for backups, monitoring, updates and a reliable hand when something breaks — others bring me in for a specific setup, migration or fix.
Can you manage a server you didn’t build?
Yes. I start with an audit — security, backups, performance, what’s fragile — then stabilize it and take over from there.
cPanel/WHM, Proxmox, plain Linux — which do you work with?
All of them, plus Docker and KVM/LXC virtualization. I’ll work with what you have rather than forcing a stack change.

Tell me what’s not working — or not talking to what.

New build, a system that needs rescuing, an integration, the June 2026 deadline. One developer who builds it and stays to run it. Reply usually within 1–2 business days.