shopify-deploy-integration
Deploy Shopify apps to Vercel, Fly.io, Railway, and Cloud Run with proper environment configuration. Use when deploying Shopify-powered applications to production, configuring platform-specific secrets, or setting up hosting. Trigger with phrases like "deploy shopify", "shopify hosting", "shopify Vercel", "shopify production deploy", "shopify Fly.io".
What this skill does
# Shopify Deploy Integration ## Overview Deploy Shopify apps to popular hosting platforms. Covers environment configuration, webhook URL setup, and Shopify CLI deployment for extensions. ## Prerequisites - Shopify app tested locally with `shopify app dev` - Platform CLI installed (vercel, fly, or gcloud) - Production API credentials ready - `shopify.app.toml` configured ## Instructions ### Step 1: Deploy App with Shopify CLI ```bash # Shopify CLI handles extension deployment and app config sync shopify app deploy # This uploads: # - Theme app extensions # - Function extensions # - App configuration (URLs, scopes, webhooks) # But NOT your web app — you host that separately ``` ### Step 2: Vercel Deployment Set environment variables, configure `vercel.json` for webhooks and function timeouts, and update `shopify.app.toml` with the Vercel URL. See [Vercel Deployment](references/vercel-deployment.md) for the complete configuration. ### Step 3: Fly.io Deployment Configure `fly.toml` with health checks and min-machines, set secrets via `fly secrets set`, and deploy. See [Fly.io Deployment](references/flyio-deployment.md) for the complete configuration. ### Step 4: Google Cloud Run Deployment Use a multi-stage Dockerfile for minimal image size, deploy with `gcloud run deploy`, and configure secrets via Secret Manager. See [Cloud Run Deployment](references/cloud-run-deployment.md) for Dockerfile and deploy commands. ### Step 5: Post-Deploy Verification Run health checks, verify webhook endpoints return 401 (no HMAC), test OAuth start, and sync app config. See [Post-Deploy Verification](references/post-deploy-verification.md) for the complete verification script. ## Output - App deployed to production hosting - Environment variables securely configured - Webhook endpoints accessible via HTTPS - Health check passing - App URLs synced to Shopify Partner Dashboard ## Error Handling | Issue | Cause | Solution | |-------|-------|----------| | OAuth redirect mismatch | App URL not updated | Update `redirect_urls` in `shopify.app.toml` and deploy | | Webhooks not received | URL not HTTPS or unreachable | Verify public URL, check DNS | | Cold start timeout | Serverless function slow | Set min instances to 1 | | CSP frame-ancestors error | Missing header | Add CSP header for `*.myshopify.com` | | `shopify app deploy` fails | CLI token invalid | Regenerate at partners.shopify.com | ## Examples ### Environment Variable Checklist ```bash # Required for all deployments: SHOPIFY_API_KEY= # From Partner Dashboard SHOPIFY_API_SECRET= # From Partner Dashboard SHOPIFY_SCOPES= # e.g., "read_products,write_products" SHOPIFY_APP_URL= # Your deployed app URL # For custom/private apps: SHOPIFY_ACCESS_TOKEN= # shpat_xxx # Optional: SHOPIFY_API_VERSION= # Default: latest stable. Update quarterly — see shopify.dev/docs/api/usage/versioning SESSION_SECRET= # For cookie signing DATABASE_URL= # Session storage ``` ## Resources - Shopify App Deployment - [Vercel Remix Deployment](https://vercel.com/guides/deploying-remix-with-vercel) - [Fly.io Node.js](https://fly.io/docs/languages-and-frameworks/node/) - [Cloud Run Quickstart](https://cloud.google.com/run/docs/quickstarts)
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.