GUIDES
LAMP is just Linux, Apache, MySQL, and PHP installed and wired together — each piece is a small, separate install, and the only genuinely fiddly part is confirming Apache is actually executing PHP rather than serving it as plain text.
httpd.conf is Apache's main configuration file — but on a server hosting more than one site, the real day-to-day editing happens in per-site virtual host files, not the main config directly.
Use the mysql client with stdin redirection or source, then add the host, charset, authentication, privilege, backup, and verification safeguards appropriate to the restore.
Apache is one of the two dominant web servers (alongside Nginx) — it receives HTTP requests and hands them off to PHP, static files, or a reverse-proxied application.
reload applies a changed configuration without dropping active connections — restart briefly takes the server down entirely, a distinction worth knowing before touching a production server.
Restricting SSH to specific IP addresses via the firewall is genuinely more effective than disabling it outright — a server with no SSH access at all can't be remotely administered when something actually needs fixing.
The Ondřej Surý PPA is what makes running several PHP versions side by side on one Ubuntu server actually practical — Ubuntu's own default repositories only ship one PHP version at a time.
A working LAMP stack setup for Ubuntu — apt package installation, the Apache/MySQL services, and the one phpMyAdmin config step people usually miss.
Ondřej Surý's PPA packages every PHP version alongside each other under version-suffixed names, letting each site on a shared server run its own PHP-FPM pool at its own version.
Three real approaches — virtual host document root, a root .htaccess rewrite, and symlinking — with the tradeoffs that actually matter for picking one.
httpd.conf holds Apache's global server settings, while individual virtual host files define how each specific domain or subdomain on that same server is actually handled.
