Web server
My own infrastructureA single server carrying forty sites, kept running by me for years.
My own projects and the sites of former clients live on this server. Setup, migration, hardening, certificates, backups and monitoring are all mine. This is what sits behind the sentence "I can handle the server side too".
40 sites
Hosted and administered on one server
100% HTTPS
With certificates that renew themselves
24/7 monitoring
So a problem is caught before you notice it
Why this is here
This is not client work either. But “servers and DevOps” appearing on a service list does not mean the person actually runs servers. On mine it does: I have been running this one for years, and I am the one who gets up when something breaks at night.
What lives on it
Alongside my own projects, the sites of clients I worked with in the past are hosted here. Around forty sites in total: corporate sites, e-commerce systems, older PHP applications and content sites. All on one machine, isolated from each other with separate users and separate PHP pools.
The work
Migration. The sites were moved from an old machine to a clean server I built from scratch. During the move, the old and new responses were compared site by site; content, URLs and admin routes came out identical.
Security. SSH is key-only on a non-standard port with root login disabled. Script execution is blocked inside upload directories, sensitive file extensions are refused, and failed login attempts are banned automatically. Administrative access also has a VPN in front of it.
Certificates. Let’s Encrypt certificates were issued for every site and renew automatically. A site whose certificate quietly expires is no different from a site that is down.
Backups and monitoring. Database and file backups run on a schedule; disk, memory and service health are watched. The goal is simple: when something breaks, I should hear about it before the client does.
The point
If a new project needs a server, I do not have to ask anyone else. I already do the same work, from provisioning to hardening, on my own infrastructure.