Shopkeeper is a CLI to help manage Shopify stores.
It is built as an oclif plugin to allow seamless integration with the Shopify CLI theme developers use every day.
It helps developers:
- Manage settings
- Deploy theme changes
You can install the CLI globally with:
npm install -g @thebeyondgroup/shopkeeper
Or if your theme has a package.json
:
npm add --save-dev @thebeyondgroup/shopkeeper
๐จ It is not currently possible to use Shopkeeper as a plugin to the homebrew installation of the Shopify CLI. To use it, you need to install it as a global npm package and use the
shopkeeper
executable.
Assuming you've set SHOPIFY_CLI_THEME_TOKEN
, SHOPIFY_FLAG_STORE
,
SHOPIFY_FLAG_PATH
, or are setting their corresponding flags when calling a
command:
To download settings from the live theme:
shopkeeper theme settings download
To switch buckets:
shopkeeper bucket switch --bucket <bucket name>
To deploy directly to the live theme after pulling down the live theme's settings:
shopkeeper theme deploy --strategy basic
For a more complete introduction and walkthrough of how to use Shopkeeper, see guide.
To learn the full capability of Shopkeeper, see the command docs.
When using it as a standalone, call commands using shopkeeper COMMAND
.
When using it as a plugin to the Shopify CLI, you can call command using shopify COMMAND
.
You can verify Shopkeeper has been correctly installed as a plugin by running shopify commands
.
If you can see the bucket commands listed, Shopkeeper is installed correctly.
Use npx
to run the version local to your project's node_modules
.
If the commands are not showing up, reinstall the package. This triggers a postinstall hook that registers Shopkeeper with the Shopify CLI.
Shopkeeper makes it easy to manage multiple Shopify stores from a single codebase. In particular, it makes it easy to switch between store instances and manage theme settings.
It uses a .shopkeeper
folder at the root of your project to store buckets of settings.
๐ง We refer to groups of settings as "buckets" because the term environment is overloaded in Shopify development. You might have production and staging store instances. These might be referred to as "environments." To add to the confusion, Shopify recently added the ability to specify groups of flags in a
shopify.theme.toml
file and calls these groups environments.Therefore, we call our groups of settings buckets. ๐ชฃ
In multi-store, multi-region setups, you might have a directory for
each region. Say canada
, united-states
, or united-kingdom
. Or you might
use a bucket to contains the settings for an A/B test.
Here we see an example production
bucket created from the default
installation of Dawn:
.shopkeeper
โโโ production
โย ย โโโ config
โย ย โย ย โโโ settings_data.json
โย ย โโโ sections
โย ย โย ย โโโ footer-group.json
โย ย โย ย โโโ header-group.json
โย ย โโโ templates
โย ย โย ย โโโ customers
โย ย โย ย โย ย โโโ account.json
โย ย โย ย โย ย โโโ activate_account.json
โย ย โย ย โย ย โโโ addresses.json
โย ย โย ย โย ย โโโ login.json
โย ย โย ย โย ย โโโ order.json
โย ย โย ย โย ย โโโ register.json
โย ย โย ย โย ย โโโ reset_password.json
โย ย โย ย โโโ 404.json
โย ย โย ย โโโ article.json
โย ย โย ย โโโ blog.json
โย ย โย ย โโโ cart.json
โย ย โย ย โโโ collection.json
โย ย โย ย โโโ index.json
โย ย โย ย โโโ list-collections.json
โย ย โย ย โโโ page.contact.json
โย ย โย ย โโโ page.json
โย ย โย ย โโโ password.json
โย ย โย ย โโโ product.json
โย ย โย ย โโโ search.json
โย ย โโโ .env
โย ย โโโ .env.sample
โโโ .current-bucket
Each folder contains theme settings stored in their corresponding config
,
sections
, and templates
folders. It also contains a .env
file that's
copied to the project root as .env
when the bucket is switched.
Shopkeeper supports multiple deployment strategies:
- Basic
- Blue/Green
Shopkeeper extends the Shopify CLI theme
topic with a
deploy
command.
When you run shopkeeper theme deploy --strategy basic
, Shopkeeper will:
- Download settings from the live theme
- Push code to the live theme
- Update the live theme's name to be
[HEAD_SHA] Production
โ ๏ธ the default deployment strategy isblue-green
, so the--strategy
must be set.
A blue/green deployment strategy alternates between a blue and a green theme. One theme is live and the other we refer to as on-deck. For example, using this approach, if a the blue ๐ต theme is live, the green ๐ข theme is on-deck.
When you run shopkeeper theme deploy
, Shopkeeper will:
- Download settings from the live theme
- Push code to the on-deck theme
- Rename the on-deck theme to be
[<HEAD_SHA>] Production - <color>
Using blue/green deploys requires additional setup. You must specify the theme IDs for the blue and green themes. You can pass these values as flags:
shopkeeper theme deploy --blue 13455343 --green 654321
A better option is to set the flags in the bucket's .env
file. Every flag in
the Shopify CLI can be set with an environment variable. Shopkeeper follows
this pattern:
Flag | Use |
---|---|
SKR_FLAG_BLUE_THEME_ID |
blue theme ID, cannot be name as name will be update |
SKR_FLAG_GREEN_THEME_ID |
green theme ID, cannot be name as name will be update |
Using a tool like direnv, you can have your environment variables automatically updated when you switch buckets.
If you'd like to contribute to the project, check out the contributors docs to get started.