Learn how to manage (build, configure, maintain, repair) your own Linux server. Course not finished recording. Once finished, price will be $300.
- Managing Linux servers, and the routine tasks of server management (build, configure, maintain, repair)
- Course assumes you already know basics of moving around the command line and making edits
This course will teach you the majority of typical day-to-day Linux management tasks. Learn how to deal with common server issues on your own, understand online Linux guides, and be more helpful when hiring someone to fix for you.
I break down the general strategies of server management: provisioning, configuring, diagnosing, and repairing. And of course, all done in WPJohnny-style. 🙂 Once you know how to THINK like a sys-admin…you’ll know how to target problems quickly, what to type into Google search, and most importantly…how to save the day for your clients!
- Setting up Linux distro on server
- Main goal of this basic Linux course (what to expect)
- Why Linux? (performance, security, open-source)
- Choosing server provider
- Choosing Linux distro (RHEL/Centos vs Ubuntu/Debian)
- Installing packages and modules.
- Script vs Scratch install (hostname & RDNS)
- VPS basics – provision, change size, delete, SSH access (pass, keys, console)
- Performance-testing
- Locations of important files & and stack-specific settings:
- website directories
- server config files (ssh, apache, niginx, ols, php, mysql)
- log files (access, error, cron, etc)
- cron
- etc
- Configuring services
- SSH config
- web server config (global vs vhost)
- mysql server config
- Monitoring services & software
- Provider UI – overview of all servers, notifications
- Server dashboard – UI &
top,htop - Monitoring software install – Monix, etc
- 3rd-party monitor services –
- Monitoring resources & processes
top
- Management tasks
- Run Linux updates (OS/kernel & software)..proactive maintenance
- Monitoring server loads & DDOS activity
- Mitigating problem sites
- Server diagnosis and troubleshooting
- Linux repair strategy (resources, configs, network, and security)…all server issues mostly come down to 4 areas…
- High CPU usage – high traffic, bad code, malware, CPU steal
- High memory usage – high traffic, bad code
- High disk usage – backups, logs, poor file management
- Network limitations – firewall block, DNS issues, or datacenter (restriction or routing issues, aka “dropped packets”)
- Security – DDOS (inbound or outbound), and/or runaway scripts or rogue processes
- Reading logs (or Log Management)
- Diagnosis strategy – Knowing which logs to read (experience and common sense)
- Access logs
- SSL logs
- service logs
- attack logs
- any other logs?
- configuring log size
- Extending with
less,tail,grep,end. (sys-admin)
- Hack repair
- Detecting hacks & plan of action
- Scanning for hacks
- Tracking down (stealth/rogue) processes.
- dfd
- MySQL shell
- Importing & exporting DB’s
- Database management via mysql shell
- Webhosting agency strategy
- Things to consider as a webhost – business & technical
Unfinished notes below…(ignore)
All fixes revolve around:
- finding the issue (diagnosing logs & processes, verbose output)
- making change or deleting files
- installing or reconfiguring services/modules
- learning from guides that don’t match your stack/config exactly
topics inside
- Systems-administrator mentality
- Finding issues under pressure.
- Building low-maintenance solutions.
- Testing server performance
- CPU over use
- bloated application
- hack
- CPU steal – talk about IP swap