orcaqubits/magento-deploy
dist/cursor/magento2-commerce/skills/magento-deploy/SKILL.md
Deploy Magento 2 — deployment modes, static content deployment, DI compilation, CLI commands, zero-downtime strategies, and CI/CD pipeline setup. Use when preparing for production deployment or building deployment automation.
$ install --global
skillsauthnpx skillsauth add orcaqubits/agentic-commerce-claude-plugins magento-deployInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 9, 2026, 6:57 AM129.3s1 file scanned
SKILL.md
- name:
- magento-deploy
- description:
- >
Magento 2 Deployment & CLI
Before writing code
Fetch live docs:
- Fetch
https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/set-modefor deployment modes - Fetch
https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/static-view/static-view-file-deploymentfor static content deploy - Web-search
magento 2 zero downtime deploymentfor zero-downtime strategies
Deployment Modes
| Mode | Errors | Static Files | DI Compilation | Use Case | |------|--------|-------------|----------------|----------| | Developer | Displayed | Generated on demand | Automatic | Local development | | Production | Logged only | Pre-deployed | Pre-compiled | Live site | | Default | Not displayed | On demand | Not optimized | Initial install |
bin/magento deploy:mode:show
bin/magento deploy:mode:set production
bin/magento deploy:mode:set developer
Production Deployment Steps
Standard Sequence
# 1. Enable maintenance mode
bin/magento maintenance:enable
# 2. Pull latest code (git pull, composer install)
composer install --no-dev --optimize-autoloader
# 3. Run setup upgrade (applies db_schema changes and patches)
bin/magento setup:upgrade
# 4. Compile DI (generates interceptors, factories, proxies)
bin/magento setup:di:compile
# 5. Deploy static content (CSS, JS, images, templates)
bin/magento setup:static-content:deploy en_US --jobs=4
# 6. Flush cache
bin/magento cache:flush
# 7. Disable maintenance mode
bin/magento maintenance:disable
Static Content Deploy Strategies
- quick — minimizes deployment time by reusing files across locales (default in 2.4+)
- compact — minimizes disk space
- standard — full deployment
- Flags:
--exclude-theme,--no-html-minify,--jobs=Nfor parallelism
Zero-Downtime Deployment
Pipeline Deployment
Build and deploy on separate systems:
- Build server:
setup:di:compile+setup:static-content:deploy - Transfer artifacts to production
- Production:
setup:upgrade --keep-generated(no recompilation)
Blue-Green Deployment
Two identical environments with load balancer switching:
- Native support since 2.4.4:
deployment/blue_green/enabledinapp/etc/env.php - Deploy to inactive environment, test, switch traffic
- Instant rollback by switching back
Symlink Switching
- Deploy to versioned directories (
releases/20260214/) - Switch
currentsymlink to new release - Shared directories for
var/,pub/media/,app/etc/env.php - Tools: Deployer (deployer.org), Capistrano, custom scripts
Essential CLI Commands
Module Management
bin/magento module:enable VendorName_ModuleName
bin/magento module:disable VendorName_ModuleName
bin/magento module:status
Cache Management
bin/magento cache:clean # Clean invalidated cache types
bin/magento cache:flush # Flush all cache storage
bin/magento cache:status # Show cache type status
bin/magento cache:enable <type>
bin/magento cache:disable <type>
Indexer Management
bin/magento indexer:reindex
bin/magento indexer:status
bin/magento indexer:set-mode schedule
Cron
bin/magento cron:run
bin/magento cron:install
Admin
bin/magento admin:user:create
bin/magento admin:user:unlock <username>
Development
bin/magento dev:profiler:enable
bin/magento dev:template-hints:enable
bin/magento setup:config:set --<option>=<value>
CI/CD Pipeline Pattern
- Lint/Static Analysis: PHP_CodeSniffer, PHPStan, Magento coding standard
- Unit Tests:
vendor/bin/phpunit -c dev/tests/unit/phpunit.xml.dist - Build:
composer install --no-dev,setup:di:compile,setup:static-content:deploy - Integration Tests (optional, slow): against test database
- Deploy: transfer artifacts,
setup:upgrade, cache flush - Smoke Test: verify critical pages load
Best Practices
- Never run
setup:di:compileorsetup:static-content:deployon production during traffic - Use pipeline deployment for zero-downtime
- Use
--jobs=Nfor parallel static content deployment - Automate deployment — manual steps are error-prone
- Always take database backups before
setup:upgrade - Test deployment on staging before production
Fetch the deployment documentation for exact CLI options, mode-switching requirements, and pipeline deployment configuration before deploying.
Related Skills
orcaqubits/spree-headless-storefront
development
VerifiedTrustedCommunity
Build with Spree's headless Next.js storefront — the official `spree/storefront` repo (Next.js 16 App Router with Server Actions and Turbopack, React 19 Server Components, Tailwind CSS 4, TypeScript 5, `@spree/sdk`, Sentry), server-only auth (httpOnly JWT cookies + publishable key), MeiliSearch faceted catalog, one-page checkout with Apple/Google Pay/Klarna/Affirm/SEPA, multi-region market routing, GA4 + JSON-LD SEO, and Vercel/Docker deployment. Use when forking or customizing the storefront, or evaluating headless adoption.
27SKILL.mdUpdated May 14, 2026
orcaqubits/spree-extensions
tools
VerifiedTrustedCommunity
Build Spree extensions as Rails engines — gem scaffolding, `bin/rails g spree:extension`, mounting routes/migrations/assets, the modern `prepend` decorator pattern (`*_decorator.rb` with `self.prepended(base)`), generators (`spree:model_decorator`, `spree:controller_decorator`), the four customization surfaces in preference order (Events > Webhooks > Dependencies > Decorators), Spree::Dependencies for swapping service objects, gem release/versioning, and the deprecated Deface engine. Use when building a reusable Spree extension or adding non-trivial customization to an app.
27SKILL.mdUpdated May 14, 2026
orcaqubits/spree-events-webhooks
development
VerifiedTrustedCommunity
Build with Spree's event bus and Webhooks 2.0 — `Spree::Events` publication, `Spree::Subscriber` DSL with `subscribes_to` and `on`, wildcard matching, lifecycle events (`{model}.created/.updated/.deleted` via `publishes_lifecycle_events`), the canonical event catalog (order.*, payment.*, shipment.*, product.*), Webhooks 2.0 endpoints, HMAC-SHA256 signing (`X-Spree-Webhook-Signature`), exponential-backoff retries, and Sidekiq job orchestration. Use when wiring event-driven business logic, building webhook consumers, or replacing ActiveSupport callback chains.
27SKILL.mdUpdated May 14, 2026
orcaqubits/spree-dev-patterns
tools
VerifiedTrustedCommunity
Cross-cutting Spree development patterns — the customization preference hierarchy (Events > Webhooks > Dependencies > Decorators), `Spree::Dependencies` service-object swapping, the `_decorator.rb` + `prepend` + `self.prepended` idiom, idempotent subscribers and webhook receivers, multi-store scoping discipline, prefixed IDs, calculator polymorphism (shipping/promotion/tax share the base), service-object composition with `dry-monads` or simple results, why to avoid `class_eval` reopening and Deface, and Spree-on-Rails idioms (Hotwire/Turbo Stimulus, ActiveStorage, Action Cable, Sidekiq). Use when designing the architecture of a Spree extension or solving cross-cutting concerns.
27SKILL.mdUpdated May 14, 2026