Deployment docker image reference

Use our simple docker container for automatic deployments from your preferred CI/CD tool. Variables for the container are described below.

Docker Image code

MWCS_DEPLOY_DEST: "/httpdocs"
MWCS_INTEGRATION_SECRET: $MWCS_INTEGRATION_SECRET
MWCS_INTEGRATION_ID: "HhYn9Per7Ni3Jhz3McVpR"
MWCS_APP_ID: "12345"
MWCS_WORKING_DIR: "/dist"
TEXT

Docker Image variables

• MWCS_DEPLOY_DEST (Required)
  • Destination path for the code to be deployed to. Examples:
  • Deploying to the app's root directory:
    MWCS_DEPLOY_DEST: "/httpdocs"
  • Deploying a WordPress theme:
    MWCS_DEPLOY_DEST: "/httpdocs/wp-content/themes/mwcs-example-theme"
• MWCS_INTEGRATION_SECRET (Required)
  • The integration secret that was created when you set up a new Git integration. For security purposes, this should always use a protected variable whenever possible. Examples:
  • As a protected variable:
    MWCS_INTEGRATION_SECRET: $MWCS_INTEGRATION_SECRET
  • As plain-text:
    MWCS_INTEGRATION_SECRET: "mysecretfromsomewhere"
  • You can get your Integration Secret from your Managed WooCommerce Stores Overview. In the Git Deploy section, for the integration you want to use, select Edit, and then next to Integration Secret, select .
• MWCS_INTEGRATION_ID (Required)
  • The integration ID that was created when you set up a new Git integration. Examples:
  • MWCS_INTEGRATION_ID: "ABCDEFGHIJKL0123456789$$"
  • You can get your Integration ID from your Managed WooCommerce Stores Overview. In the Git Deploy section, for the integration you want to use, select Edit, and then next to Integration ID, select .
• MWCS_APP_ID (Required)
  • ID of the app that you will be deploying to. Example:
  • MWCS_APP_ID: "12345"
  • You can find the MWCS_APP_ID value in your Managed WooCommerce Stores Overview. In the Git Deploy section, next to Production Id or Staging Id select . For example, you could set up one branch to deploy to your staging site, and another branch to deploy to production.
• MWCS_WORKING_DIR (Optional)
  • Working directory to be deployed. If left empty, uses your CI/CD tool's default directory. It is useful for deploying from a different directory inside your build environment, such as when the repository needs to be built before deploying. Examples:
  • Using Bitbucket's default clone directory variable:
    MWCS_WORKING_DIR: $BITBUCKET_CLONE_DIR
  • Using a manually defined build path:
    MWCS_WORKING_DIR: "/dist"

More info

• Learn how to create a Git integration for your Managed WooCommerce Stores site.
• Get details on setting up GitHub for automatic deployments to your site.
• Find out about key concepts for setting up the GitHub repository for automatic deployments.