Deployment

There is no single deploy. The theme deploys through Shopify's GitHub connection, each Cloud Run service is released from its own repository, and Zapier and Zoho are changed in their own dashboards.

Theme

A Shopify theme is connected to the main branch of Conversion-Kings/asc-shopify-theme through Shopify's GitHub integration. Its commits appear in git history as "Update from Shopify for theme australian-sports-camps/main". That name dates from before the repository was renamed.

The connection works in both directions:

• A merge to theme main updates the connected theme.
• A save in the theme editor or the Admin code editor on that theme becomes a shopify[bot] commit on main. Since September 2025 this has included edits to Liquid files, not only JSON templates and settings.

Feature branches are often connected to their own unpublished themes for review. Bot commits named asc-shopify-theme/<branch> come from those.

asc-shopify-src has no deployment of its own. Its only effect on the storefront is through the files webpack writes into theme/assets/.

The steps for developers are in Releasing a change.

Branches

documentation/TECHSTACK.md describes develop and staging themes. No develop branch exists in either repository, and bot commits to staging and develop themes stopped in October 2024.

The "Merge main to staging" workflow in asc-shopify-src also tries to merge into dev-content and dev-seo. Neither branch exists, so every run fails after the staging step. The staging merge still succeeds.

asc-api-membership-pass

The repository Conversion-Kings/asc-api-membership-pass has build and test scripts but no Dockerfile or deployment script. How it is released to Cloud Run is not recorded in a repository. Check the service's revision history in the Google Cloud console.

It needs these environment variables, set on the Cloud Run service: SHOPIFY_STORE_NAME, SHOPIFY_ACCESS_TOKEN, SHOPIFY_STOREFRONT_ACCESS_TOKEN, ONLINE_STORE_PUBLICATION, API_PUBLICATION. With NODE_ENV=gcloud it writes JSON logs to a mounted Cloud Storage volume.

shopify-zoho-integration

The repository's docker-release script builds the image and pushes it to Artifact Registry as australia-southeast1-docker.pkg.dev/asc-map-project/asc-packages/shopify-zoho-integration:latest. It does not create a Cloud Run revision. A new revision is deployed from the Google Cloud console. The detailed steps are in docs/deployment.md in that repository.

There is no staging Zoho organisation. Test orders are processed into live Zoho unless the order's custom.environment metafield marks them as another environment.

Legacy gcloud-api

npm run gcloud-api:build in this repository builds google-cloud-api/ and pushes asc-packages/gcloud-api:latest. The storefront has not called that service since 10 June 2026. Do not release it. See Legacy and unused code.

Zapier and Zoho

Zaps are edited in Zapier. Zoho workflow rules, functions and schedules are edited in Zoho CRM settings.

misc/deluge-scripts/ holds copies of the Zoho functions. They are updated by hand, the latest in August 2026, so treat them as a record rather than the deployed version.

Rollback

Steps are in Deploy and roll back.