DevOps & Server Administration
DevOps connects application code with the systems that build, run, measure, and recover it. For a small web application, that work includes terminal access, process and proxy configuration, caching, observability, backups, and tested recovery steps.
This hub routes each task to a focused guide. Start with the terminal guides if command-line work is new, then choose the server topic that matches the system in front of you.
Start Here
- The Terminal: A Practical Guide teaches shell navigation, file operations, pipes, redirection, and safe command habits.
- Terminal Commands: A Practical Reference provides task-organized examples and expected output for common shell commands.
- Using AI Coding Agents in the Terminal covers project scope, approvals, command review, and checking changes made by terminal agents.
Choose a DevOps Guide
- Server Statistics and Observability explains metrics, logs, traces, browser timing, host pressure, and alerts tied to decisions.
- Server Contingency Planning turns failure scenarios into owned restore, rollback, communication, and verification steps.
- Squid Caching Proxy covers proxy roles, access controls, cache behavior, and the cases where Squid still fits.
Related Programming Guides
- Backend development explains the server-side code and data layer that DevOps keeps running.
- PHP programming covers the web applications behind many server-administration tasks.
- SQL programming covers database design, queries, indexes, and transactions that affect operational health.
- APIs covers service contracts, retries, callbacks, and integration logging.
Frequently Asked Questions
What is the difference between DevOps and system administration?
Traditional administration is a separate team keeping servers running after developers hand over finished code. DevOps merges the two responsibilities, so the people who build a system also help run, monitor, and repair it in production.
Do you need Docker to learn DevOps basics?
No. Terminal fluency, process management, logging, and recovery planning apply whether the application runs in a container, a virtual machine, or directly on a server. Containers are a deployment choice on top of those fundamentals.
What is the difference between uptime and reliability?
Uptime says whether a service is running. Reliability says whether it does its job correctly and consistently, so a server can show perfect uptime while timing out, failing requests, or returning wrong data.
What does infrastructure as code mean?
Defining servers, networks, and configuration in version-controlled files that a tool applies, rather than clicking through a control panel or running one-off commands. The environment can then be rebuilt or audited from the files themselves.
Should logging live in the application or on the server?
Both, for different reasons. Application logs capture business events and request context only the code knows. Server and process logs capture crashes, restarts, and resource limits the application cannot see from inside itself.
Read Next
Learn how terminals and shells work, navigate files, use core Unix commands, connect commands with pipes, and supervise terminal-based coding agents.
Learn how to start terminal AI coding agents in the right project, supervise commands, review file changes, and set safe working boundaries.
Replace old PHP uptime scripts with useful server statistics: metrics, logs, traces, browser timing, and alerts that explain production behavior.
Build a server contingency plan around impact, backups, restore tests, rollback paths, ownership, and maintenance.
Understand what Squid still does well, where HTTP caching has moved, and how to think about proxies without treating cache as magic.