June 1, 2023 - Note that Shopify 2.0 is deprecated and will be sunset on May 31, 2023. We encourage using Shopify CLI 3.0 to develop apps, custom storefronts, and themes.
As of Shopify CLI version 3.59.0, you no longer need to install the @shopify/app package as it is bundled with @shopify/cli.
Discussions
shopify-cli-2.1.0.deb => new shopify-cli package pre- ...
I am trying to install the Shopify-cli-2.1.0.deb , But I am receiving the error. I already executed the command sudo gem update --system 3.1.3 sudo apt-get install -y ruby-dev but when I am trying to More on stackoverflow.com
stackoverflow.com
August 31, 2021
homebrew - Shopify CLI seems unable to find Ruby on Mac - Stack Overflow
I installed shopify-cli using homebrew on my Mac and tried verifying the installation by running shopify version, but I get an error: /usr/local/bin/shopify: line 2: /opt/homebrew/Cellar/ruby/3.0.1... More on stackoverflow.com
stackoverflow.com
linux - Can't install Shopify CLI on Ubuntu 20.04 - Stack Overflow
Results logged to /var/lib/gem... while processing: /home/stefan/Downloads/shopify-cli-2.6.3.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ... sudo apt update sudo apt install ruby-full ruby --version sudo apt update sudo apt install git curl autoconf ... More on stackoverflow.com
stackoverflow.com
GitHub with Shopify CLI Workflow Help
I'm a relative noob and just got my process nailed down the other day... after a week of mucking around with it all accompanied by loud, extended slurs of my favorite profanities. I've used it in real life for the development and deployment of 3 separate "features" since then and all seems to be well. Pros, feel free to make suggestions to make things go a little smoother - be nice... as I said, I'm a relative noob as well and might not have it nailed 💯 yet. This is my Git setup/workflow that comes into play after you have successfully set up Shopify CLI. It assumes you have a repository for your project (along with a 'main' branch) created in Github and were able to get the theme files onto your local machine. If you need help getting to there, let me know and I'll try to find the article i followed to get myself there - it was very straight forward. on your local machine, cd into your project directory (i.e. where your theme code resides) git init git branch -M git push --set-upstream origin main git add . git commit -m "Initial Add theme files to remote repository" git remote add origin https://github.com/[YOUR_GITHUB_USERNAME]/main.git git push -u origin main At this point, all of your theme files should now be able to be viewed in GitHub under the 'main' branch In Shopify Admin --> Online Store: Click 'Add Theme' and choose 'Select From GitHub' log into GitHub, authorize permissions and choose the repositories you want to be available to THIS Shopify shop choose the repository you just pushed your theme files to (Step #7 above) click 'Connect' (be sure it shows 'main' as the branch you're connecting to) At this point, you will notice a newly added theme at the top of your Theme Library - it should be named '[REPOSITORY_NAME/main'. Publish it (without Git, obviously you should be sure to make a backup copy of your Current Theme anytime you overwrite it) Now your Current Theme is linked to the 'main' branch of your project's repository on GitHub. Anytime you push changes to that branch (on GitHub), they will be reflected in the live, current version of your Shopify shop. In order for those changes to be deployed, you have to push them from your local up to GitHub (#7 above). Before you do that, the changes will only be viewable on your local preview that you'll create using Shopify CLI (read on) On your local machine, from the dir from #1 above, git checkout -b staging - this will create a new branch, 'staging', from 'main' and switch to it git add . git commit -m "Initial add theme files to staging branch remote repository" git remote add origin [https://github.com/[YOUR_GITHUB_USERNAME]/staging.git git push -u origin staging At this point, all of your theme files should now be able to be viewed in GitHub under the 'staging' branch In Shopify Admin --> Online Store: 5. Click 'Add Theme' and choose 'Select From GitHub' 6. You should still be signed into GitHub. If you're not, see #10 above. Once signed in, select your account and repository and this time click the 'Connect' button across from 'Staging'. At this point, you will notice a newly added theme at the top your Theme Library - it should be named '[REPOSITORY_NAME]/staging'. NOTE: Steps 1 - 19 above are only necessary the 1st time you do all of this. Moving forward, your connections (in Shopify Admin Dashboard) to the 'main' and 'staging' branches (in GitHub) should stay intact until you disconnect them. So next comes, creating branches for edits/features/bugs/whatever and getting them through the deployment pipeline. on your local machine, cd into your project directory (i.e. where your theme code resides) git checkout staging git pull git checkout -b feature/[YOUR_FEATURE_NAME] get add . git commit -m "Initial Add theme files to [YOUR_FEATURE_NAME] branch" git remote add origin https://github.com/[YOUR_FEATURE_NAME]/main.git git push -u origin feature/[YOUR_FEATURE_NAME] from the directory in #1 above, Shopify theme dev- this will start your LOCAL dev server. It will allow you to view front end changes such as the final HTML/CSS output by the Shopify app to your browser. It also **kind of ** creates another theme in your Theme Library that you can make changes to (either through code or through the Online Customizer) and then preview (or send to your clients for them to preview) on the Shopify server. There should be links to all 3 of these things (local preview, Shopify Theme Library Preview and Shopify Theme Library Customizer) right below wherever you typed: Shopify theme dev in your terminal I say "kind of" because while you can edit and preview that backup theme via the 3 links provided per step #9, you won't actually SEE an additional theme added to the Theme Library. Since you have the 3 links in your terminal, there's no real need... especially since you won't ever directly be publishing that code - instead it will come from GitHub... more on that in a minute. Continue to make edits for this feature locally, previewing locally, pushing changes to the corresponding remote feature branch with git push and previewing on Shopify server. Your changes will not be reflected on the Shopify preview server until you push them to the remote repository... #8 above. Once you are satisfied with your changes and think they're ready to be moved to the Staging server for official QA/UAT (or whatever processes your company goes through in this circumstances): 2. initiate a Pull Request for the changes you just completed and pushed - it should be a request to merge your feature branch INTO 'Staging' jump through whatever hoops your organization requires and once it is approved, from the dir from #1 above: Shopify theme dev. This will provide you with local and Shopify-server versions of the shop in its Staging environment. Use thse links to do what you need to do for approvals from managers or any other stakeholders. When all the conditions that need to be met (according to your company policy) in order for this new future to "go live" are met, make one final Pull Request to merge 'Staging' branch INTO 'main' Once your changes have been verified in Production (i.e. the LIVE version of your shopify shop, you can/should remove any branches created for those changes, always leaving 'staging' and 'main' -- from the dir from #1 above: git checkout -d [YOUR_FEATURE_NAME] git push origin --delete feature/[YOUR_FEATURE_NAME] I hope this is helpful. If you need more detail on any of the steps, feel free to ask. I'll explain the best understanding I have of it and others may chime in with mre complete (or more correct) explainations. More on reddit.com
September 15, 2018 - Command line tools for Shopify. Latest version: 1.0.11, last published: 7 years ago. Start using shopify-cli in your project by running `npm i shopify-cli`. There are 0 other projects in the npm registry using shopify-cli.
June 1, 2023 - GPG key ID: 4AEE18F83AFDEB23 · Expired · Verified · Learn about vigilant mode. Compare · Filter · Loading · There was an error while loading. Please reload this page. View all tags · Version 2.36.0 Latest ·
August 25, 2020 - In this article, we’ll go through some of its features of version 1.1 (the latest at the time of writing), so you can leverage it in your development process when building new apps.
April 23, 2021 - Usage: shopify generate [ billing | page | webhook ] open: Open your local development app in the default browser. ... serve: Start a local development node server for your project, as well as a public ngrok tunnel to your localhost. ... Let me know what do you think of this CLI if you have used it, if you had some difficulties you can check the original Shopify documentation about it.
March 22, 2022 - Latest version: 0.12.1, last published: 3 years ago. Start using @shopify/hydrogen-cli in your project by running `npm i @shopify/hydrogen-cli`. There are no other projects in the npm registry using @shopify/hydrogen-cli.