Skip to content

Quick Start

This page gets you from zero to a working, near-100-Lighthouse Magento store in about 60 seconds of terminal time. It assumes you already have a Magento store running somewhere.

Note

You need DragonflyDB installed before Accelerate Guru can cache anything. If you haven't installed it yet, do that first: DragonflyDB Setup. The quick path below includes the one-liner for Ubuntu/Debian.


#Step 1 — Install DragonflyDB (if not already running)

# Ubuntu / Debian
curl -fsSL https://packages.dragonflydb.io/gpg | sudo gpg --dearmor -o /usr/share/keyrings/dragonflydb.gpg
echo "deb [signed-by=/usr/share/keyrings/dragonflydb.gpg] https://packages.dragonflydb.io/apt stable main" \
  | sudo tee /etc/apt/sources.list.d/dragonflydb.list
sudo apt update && sudo apt install -y dragonflydb
sudo systemctl enable --now dragonflydb

# Verify
redis-cli ping   # → PONG

#Step 2 — Install Accelerate Guru

curl -fsSL https://accelerate.guru/install | sudo sh

What the installer does:

  1. Detects your OS and CPU architecture (Linux/macOS, x86_64/aarch64).
  2. On Linux x86_64, checks /proc/cpuinfo for AVX2 support and downloads the optimised binary automatically.
  3. Downloads the release tarball and verifies its SHA-256 checksum.
  4. Installs the binary to /usr/local/bin/accelerate-guru.
  5. Runs accelerate-guru install to register the systemd (Linux) or launchd (macOS) service.
  6. Seeds a default magento_ultra.ini into /etc/accelerate-guru/ if one doesn't exist yet.
  7. Checks whether DragonflyDB is reachable on localhost:6379 and warns if not.

Expected output:

==> Detected: linux/x86_64 (glibc) [AVX2]
==> Downloading https://accelerate.guru/dist/latest/accelerate-guru-linux-x86_64-glibc-avx2.tar.gz
==> Verifying SHA-256 checksum
==> Extracting
==> Installing to /usr/local/bin/accelerate-guru
==> DragonflyDB detected on localhost:6379 — caching enabled.
==> Registering system service via 'accelerate-guru install'
==> Config placed at /etc/accelerate-guru/magento_ultra.ini — edit before starting.
==> Done. Edit your magento_ultra.ini, then:
==>   systemctl status accelerate-guru

#Step 3 — Configure

Edit /etc/accelerate-guru/magento_ultra.ini. The minimum you must change:

[server]
; Where Magento is running (host + port that serves HTTP)
upstream_addr = 127.0.0.1
upstream_port = 8080        ; ← change to your Magento HTTP port

[license]
key = YOUR-LICENSE-KEY       ; ← paste your key from accelerate.guru/dashboard
                             ;   or use "dev" for local/staging testing

Tip

Use dev as the license key for any hostname ending in .test, .local, .internal, or .dev. These are always free and never require activation.

Save the file. The configuration is hot-reloaded — no restart needed.


#Step 4 — Start the service

sudo systemctl enable --now accelerate-guru
sudo systemctl status accelerate-guru

Expected output:

● accelerate-guru.service — Accelerate Guru — ultra-high performance Magento reverse proxy
     Loaded: loaded (/etc/systemd/system/accelerate-guru.service; enabled)
     Active: active (running) since ...

The edge is now listening on port 80 (HTTP) and port 443 (HTTPS).


#Step 5 — Point your traffic at the edge

If Magento was previously listening on port 80/443 directly, you need to move it to a different port (e.g., 8080) so Accelerate Guru can take those ports. Set upstream_port = 8080 in the config.

If you're running behind a load balancer or CDN, update the backend/origin address to point at the Accelerate Guru server instead of Magento directly.


#Step 6 — Run the health check

accelerate-guru check --url https://yourstore.com

This command fetches your homepage through the proxy, inspects headers and response content, compares it against a direct origin fetch, and reports:

  • Cache status (X-Cache: HIT / MISS)
  • Compression in use (content-encoding: zstd)
  • Image optimisation active
  • Any JavaScript console errors introduced by the proxy
  • CORS issues, TTFB measurements, and more

#Step 7 — Visit the dashboard

Open https://yourstore.com/stats-ag in your browser (from an IP listed in stats.allowed_ips — by default only 127.0.0.1).

You'll see:

  • Live cache hit rate
  • Requests per second, response times
  • Bytes saved by compression and image optimisation
  • WAF blocks and bot detections
  • Current configuration with toggle controls

#What just happened

In six steps you have:

BeforeAfter
Every request hits Magento PHP90–95% answered from DragonflyDB in ~2 ms
Images served as JPEG/PNGImages encoded as AVIF (background), 60–96% smaller
Responses compressed with gzipResponses compressed with zstd (30–40% better ratio)
No bot filteringWAF scores every request, blocks known-bad traffic
No speculative prefetchSpeculation rules prerender the next page
No service workerService worker caches assets locally, refreshes on change

#Next steps