Local machine setup
Run the whole platform on your own computer — to evaluate it, build a demo, or customise safely before going live.
Any local stack that gives you PHP 7.4 or newer (8.2 recommended), MySQL or MariaDB, and Apache or Nginx works. The recipes below use the most common one per operating system. Each ends with a plain WordPress site; installing Quickmunch into it is the same everywhere.
Windows — XAMPP
- Install XAMPP (a PHP 8.2 build) and start Apache and MySQL from its control panel.
- Raise the PHP limits first — XAMPP's defaults refuse the theme upload. Open
C:\xampp\php\php.ini, set these values, and restart Apache:upload_max_filesize = 64M post_max_size = 64M memory_limit = 256M max_execution_time = 300 max_input_vars = 3000 - Download WordPress from
wordpress.org and
extract it into
C:\xampp\htdocs\— for exampleC:\xampp\htdocs\quickmunch\. - Open phpMyAdmin (
http://localhost/phpmyadmin) and create an empty database. - Browse to
http://localhost/quickmunchand follow WordPress's own setup. Database host islocalhost, userroot, empty password.
intl, enable it in the same
php.ini by removing the leading ; from extension=intl, then
restart Apache.macOS — Local, MAMP or Homebrew
- Install a stack. Local is the simplest: it creates a WordPress site in one
step, database included, so you can go straight to step 4. MAMP, or Homebrew's
php+mysql+httpd, work too. - For MAMP or Homebrew, download WordPress and place it in the stack's web root (MAMP:
htdocs). - Create an empty database — MAMP ships phpMyAdmin; with Homebrew use
mysql -u rootandCREATE DATABASE quickmunch;— then open the site and follow WordPress's setup. - Check the upload limit: the upload screen under Media prints the maximum. If it is below 64M, raise it in the stack's PHP settings.
Linux — LAMP
- Install the stack, e.g. on Ubuntu:
sudo apt install apache2 mysql-server php8.2 php8.2-mysql php8.2-mbstring \ php8.2-gd php8.2-curl php8.2-xml php8.2-zip php8.2-intl libapache2-mod-php8.2 sudo a2enmod rewrite && sudo systemctl restart apache2 - Download WordPress into the web root and make it writable by the web server:
cd /var/www/html sudo wget https://wordpress.org/latest.tar.gz && sudo tar -xzf latest.tar.gz sudo mv wordpress quickmunch && sudo chown -R www-data:www-data quickmunch - Create the database:
sudo mysqlthenCREATE DATABASE quickmunch; CREATE USER 'qm'@'localhost' IDENTIFIED BY 'choose-a-password'; GRANT ALL ON quickmunch.* TO 'qm'@'localhost'; - Allow
.htaccessoverrides for the folder (AllowOverride All) — WordPress writes its permalink rules there — raise the PHP limits in/etc/php/8.2/apache2/php.ini, then open the site and follow WordPress's setup.
With WP-CLI
If you already use WP-CLI, the WordPress part is three commands from an empty folder:
wp core download
wp config create --dbname=quickmunch --dbuser=root --dbpass=
wp core install --url=http://localhost/quickmunch --title=Quickmunch --admin_user=you --admin_email=you@example.com
Without --admin_password, WP-CLI generates one and prints it. Nothing in Quickmunch
needs WP-CLI afterwards; it is only a faster way to reach a blank site.
After WordPress installs
Continue with Installing Quickmunch. Local sites skip HTTPS, so
features that need a secure origin — online card fields, push notifications, the installable app
— stay quiet until you are on a real domain. Payment gateways also cannot reach
localhost to confirm a payment, so a test payment can succeed at the gateway while the
order waits for a confirmation that never arrives. Everything else behaves exactly as production
does.