Extends the dev:tests:run command to execute static, unit, integration, and integrity test suites in parallel via ParaTest, with --processes and --runner options and full --arguments passthrough. Includes Composer install steps and CLI examples for speeding up local and CI pipelines.
One-command install scripts spin up a full local stack for 2.4.8 with optional sample data, plus Xdebug, Redis/Valkey, Logstash, and an optional Jenkins container for CI/CD.
Prebuilt CI pipelines (MageCheck Extension/Store) plus individual actions for setup, caching, version detection, coding standards, DI compile, and Sansec eComscan. Plug them into your repo to run quality checks and installs on GitHub with minimal configuration.
One-command installer that provisions a hardened LEMP web stack with Nginx, MariaDB, PHP-FPM, Varnish, Redis, OpenSearch, RabbitMQ, and Let’s Encrypt on Debian/Ubuntu. Also outlines SSL setup and a zero-downtime deployment pattern (current/releases/shared) with GitHub Actions.
Registry of Cursor plugins providing skills and rules for Hyvä themes, the Horizon storefront stack, and shared frontend foundations. Covers module scaffolding, Tailwind builds, Playwright tests, XSS best practices, and includes validation scripts and a GitHub Action to sync vendor skills.
CLI that polls KEV, NVD, GHSA, OSV, and Packagist, filters results against your composer.lock, and scores with CVSS/EPSS/KEV. Sends only P0/P1 alerts to Slack and returns exit codes for CI gating.
Provisions a full DDEV environment for versions 2.3–2.4.x with selectable PHP, database, Composer, and optional Varnish, then outputs the site URL. Includes examples for running CLI/DDEV commands, MFTF, and module tests in CI.
Most Magento developers spend hours manually checking robots.txt, schema markup, and sitemap configurations.
Then they wonder why their store still doesn’t appear in ChatGPT or Gemini recommendations. There is now a faster way.
This repository is a lightweight starting point for teams that want a repeatable GitHub Actions pipeline for provisioning and updating Adobe API Mesh configurations. Fork it, drop in your mesh definition files, wire up the required Adobe Developer Console credentials, and you will have a push-button deployment path for staging and production meshes.
This post explains how to set up a deployment workflow for a project using Deployer and GitLab Pipelines, including steps to build a new release, package it, and deploy it to a server via SSH. The article outlines creating a custom Docker image, configuring SSH access, and defining a .gitlab-ci.yml file to automate the deployment process. It serves as a guide for developers looking to implement similar workflows.