Once the site is live, maintenance becomes a routine rather than a one-time project.
You should be able to explain the server current health, last backup, last update, and any recent configuration change.
Step-by-step
Check free disk space
Watch both the root filesystem and the home/site storage so logs and backups cannot silently fill the disk.
df -hCheck memory and load
Use basic Linux tools to notice unusual resource growth.
free -h
uptime
topReview failed services
Look for units that are not running as expected.
systemctl --failedReview temperatures
On Raspberry Pi OS, check CPU temperature during normal and busy periods.
vcgencmd measure_tempApply updates on a schedule
Update Linux, WordPress, themes, and plugins regularly. Back up before significant changes.
Watch certificates and DNS
Record certificate expiration dates and verify that any dynamic public-IP update process is still working.
Document changes
Keep a simple change log. When something breaks months later, knowing what changed is often more useful than another monitoring graph.
You should be able to explain the server current health, last backup, last update, and any recent configuration change.
Troubleshooting
If a command or screen differs from the lesson, stop and verify the version you are using before forcing a change.
What you learned
You now understand the purpose of this part of the system and have a concrete result you can verify before continuing to the next lesson.