LAMP Stack Setup

Last updated: March 23, 2026 · 2 min read

Server & Infrastructure

LAMP Stack Setup

Standing up a LAMP stack takes about twenty minutes if you follow a
tutorial. Getting it configured correctly — for production, for security, for the specific PHP application you’re running — takes longer and requires decisions that don’t show up in the tutorial. Default configurations expose server info, aren’t sized correctly, and are dangerous precisely because they cause no immediate problems.

We set up LAMP stacks with production-appropriate configuration from the start – the right PHP version, Apache virtual hosts with correct permissions, MySQL sized for the actual server, and SSL configured before the first request arrives.

Apache vhosts, mod_rewrite, and hardening
MySQL/MariaDB sized for your server RAM
PHP 7.4–8.3, OPcache, production php.ini
Let’s Encrypt SSL with auto-renewal
UFW firewall and SSH key hardening
Configuration documentation delivered on completion

Need a LAMP stack set up?

[mmedia_services_wizard id=”lamp-stack-setup”]

How it works
Step 1
Scope the setup

Server specs, OS preference, PHP version needed, and what application you’re deploying on top.

Step 2
Stack installation

Apache, MySQL/MariaDB, and PHP installed with production-appropriate configuration for each component.

Step 3
Hardening and SSL

UFW firewall, SSH key auth, fail2ban, Let’s Encrypt certificate, HTTPS redirect, HSTS header.

Step 4
App deploy and docs

Application installed and verified running. Configuration document delivered with all decisions and file locations.

Application Installation Included

If you’re running WordPress or another PHP application on top of the stack, we deploy and verify the application as part of the same engagement. WordPress core, wp-config.php, permalink structure, and initial plugin setup if needed — all handled before handoff.

Why M Media
Production-first config

We don’t deliver tutorial configurations. Every component is tuned for production use before handoff.

Security from day one

Firewall rules, SSH hardening, and fail2ban are part of every setup – not optional add-ons.

Right PHP version

7.4 through 8.4 – we install the version your application needs with correct OPcache configuration.

Database tuned to your server

innodb_buffer_pool_size, max_connections, and slow query logging configured for actual server RAM.

SSL included

Let’s Encrypt certificate with auto-renewal, HTTPS redirect, and HSTS header – all set up during the engagement.

Delivered with docs

Configuration document details every decision, relevant file paths, and how to make common changes safely.

←
Back to Server & Infrastructure

❌
Subscription Hell
  • • Payment fails? App stops
  • • Need online activation
  • • Forced updates
  • • Data held hostage
✓
M Media Way
  • • Buy once, own forever
  • • Works offline
  • • Optional updates
  • • You control your data

Simple Licensing. No Games.

We don't believe in dark patterns, forced subscriptions, or holding your data hostage. M Media software products use clear, upfront licensing with no hidden traps.

You buy the software. You run it. You control your systems.

Licenses are designed to work offline, survive reinstalls, and respect long-term use. Updates are optional, not mandatory. Your tools don't suddenly stop working because a payment failed or a server somewhere changed hands.

✓ One-time purchase, lifetime access
✓ No "cloud authentication" breaking your workflow
✓ Upgrade when you want to, not when we force you
✓ Software empowers its owner — not rent itself back
🤖
Support Bot
"Have you tried restarting your computer? Please check our knowledge base. Your ticket has been escalated. Estimated response: 5-7 business days."
❌ Corporate Script Theater
👨‍💻
Developer (M Media)
"Checked your logs. Line 247 in config.php — the timeout value needs to be increased. Here's the exact fix + why it happened. Pushed a patch in v2.1.3."
✓ Real Technical Support

Support From People Who Understand the Code

Ever contact support and immediately know you're talking to someone reading a script? Someone who's never actually used the product? Yeah, we hate that too.

M Media support means talking to developers who wrote the code, understand the edge cases, and have probably hit the same problem you're dealing with. No ticket escalation theatrics. No "have you tried restarting?" when your question is clearly technical.

Documentation written by people who got stuck first. Support from people who fixed it.

We don't outsource support to the lowest bidder or train AI on canned responses. When you ask a question, you get an answer from someone who can actually read the logs, check the source code, and explain what's happening under the hood.

✓ Real troubleshooting, not corporate scripts
✓ Documentation that assumes you're competent
✓ Email support that doesn't auto-close tickets
✓ Updates based on actual user feedback