GNU/Linux administration
Server setup and maintenance: Nginx, PM2, access and updates
- GNU/Linux installation and configuration
- Nginx as a reverse proxy and PM2 for processes
- Users, SSH access and permissions
- Package updates and log rotation
// service · servers and infrastructure
Linux servers under control, infrastructure from configuration in Git, monitoring, backups and protection
I administer GNU/Linux and build infrastructure as code: Docker and Docker Compose, Nginx and PM2, CI/CD (build and delivery), deployment. I set up Zabbix and ELK (Elasticsearch) monitoring, backups and failover, and DDoS protection, from a single server to a multi-service platform
Server setup and maintenance: Nginx, PM2, access and updates
Docker, Docker Compose and environment configuration versioned in Git
Zabbix and ELK, alerts, backups and recovery checks
Failover, DDoS protection, cloud migration
Inventory of servers, services, access and failure points
Production environment diagram, work order, schedule and risks
Servers, IaC, monitoring, backups and protection
Incident response, updates and further development
Nginx, Redis, Zabbix and DDoS protection around microservices and real-time web consoles
case 03 · lead full-stack
9 microservices, Docker and Traefik: infrastructure for campaigns, wallet and anti-fraud
case 01 · full-stack + infrastructure
Background worker with checks, statuses and email notifications
project · full-stack
Administration is setting up and running live servers. IaC describes environments as configuration in Git, so the environment is reproducible instead of assembled by hand
Yes. I start with an inventory of servers, services, access and backups, then fix the failure points and the work plan
First an audit of the current setup and its dependencies, then the target diagram and the move of data and services, followed by scenario checks after the migration
Zabbix and ELK monitoring, alerts, backups with recovery checks, updates and DDoS protection