Coder Social home page Coder Social logo

shopware-cli's Introduction

Shopware CLI

Hosted By: Cloudsmith

A cli which contains handy helpful commands for daily Shopware tasks

Features

  • Manage your Shopware account extensions in the CLI
  • Build and validate Shopware extensions

For docs see here

Contributing

Contributions are always welcome!

shopware-cli's People

Contributors

actions-user avatar amenk avatar aragon999 avatar christian-rades avatar deepsource-autofix[bot] avatar deepsourcebot avatar dependabot[bot] avatar frosh-ci avatar janbuecker avatar jmatthiesen81 avatar jnoack331 avatar kleinmann avatar kurtinge avatar lutek avatar m-arcus avatar marcelbrode avatar niklaslimberg avatar nussjustin-hmmh avatar philipreinken avatar renovate[bot] avatar schrank avatar scriptibus avatar seggewiss avatar shyim avatar tinect avatar vanwittlaer avatar wannevancamp avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

shopware-cli's Issues

Extension Manager for Project

Please describe the feature you would like to see implemented.

  • Install
  • Uninstall
  • Activate
  • Deactivate
  • Update
  • Upload extension
  • Delete extension

build target wrong folder

PHP Version

Shopware Version

Actual behaviour

storefront is built into folder ResourcesResources

Expected behaviour

storefront is built into folder Resources

Steps to Reproduce?

Build a plugin with storefront-stuff.

Update docs

Please describe the feature you would like to see implemented.

Add docs for all commands.

shopware-cli extension admin-watch MyPlugin http://localhost is missing at least.

0.1.52 disable_ssl_check

Please describe the feature you would like to see implemented.

curl: (60) SSL certificate problem: unable to get local issuer certificate

Can we somehow ignore any type of ssl-error? :-)

Completion scripts show shopware-cli instead of shopware

PHP Version

No response

Shopware Version

No response

Actual behaviour

the completion script for bash (I assume others too) are based on command shopware-cli, but it should be shopware

Expected behaviour

print and use correct command. Use shopware-cli [command] or shopware [command] all over.

Steps to Reproduce?

install bash completion script and seeing not having auto-completion

Add support for Github releases

Please describe the feature you would like to see implemented.

Create a Github Release after Uploading the Zip to the Store

Validation command does not show same errors as check on upload

PHP Version

7.4

Shopware Version

No response

Actual behaviour

  1. The automatic code review finds a parsing error, which the validation command does not find.
  2. The automatic code review mentions missing shopware/core package, which is removed during the creation of the zip file

image

image

Expected behaviour

  1. Either:
    • The error in the code review is not valid and can be ignored
    • The error should be shown during validation
  2. The require is not removed during the creation of the zip file

Steps to Reproduce?

  1. Clone repository: https://github.com/findologic/plugin-shopware-6 (develop branch)
  2. Add required shopware requirement to composer.json (usually done during build process)
    • "shopware/core": "^6.4.6"
  3. shopware-cli extension validate plugin-shopware-6
  4. shopware-cli extension zip plugin-shopware-6
  5. Not sure how you can check the automatic code review, I uploaded it as new version

MySQL dump without config

PHP Version

No response

Shopware Version

No response

Actual behaviour

MySQL Dump should work without a config

Expected behaviour

just works

Steps to Reproduce?

PrepareFolderForZipping filter option

Please describe the feature you would like to see implemented.

Please add possibility to specify composer packages to be filtered out as well.
Additionally, to filterShopwareRequires.

So, we can use preparation without any plugin-dependency to be installed into plugins vendor.

unzip: command not found

Question

After packaging the extension, we unpack the zip to remove some files and then expose the extension main folder as artifact to GitLab.
This doesn't work anymore, since unzip is no longer available (entry point was /bin/sh -c before).

$ shopware-cli --version
shopware-cli version 0.1.54
[...]
$ unzip $EXT_INTERNAL_NAME-package.zip
/bin/bash: line 131: unzip: command not found
  1. is there a way to get unzip back working?
  2. is there a better way of doing this?
build:package:
  image:
    name: ghcr.io/friendsofshopware/shopware-cli:v0.1-phpv8.1
    entrypoint: [ "/usr/local/bin/entrypoint.sh" ]
  tags:
    - docker
  variables:
    FILE_NAME: $BASE_FILE_NAME.zip
    EXT_INTERNAL_NAME_PATTERN: -package.zip
  artifacts:
    name: $BASE_FILE_NAME
    paths:
      - "*"
  stage: build
  script:
    - shopware-cli --version

      #package the extension (executes prepare, build & zip)
    - shopware-cli extension zip ./ package --disable-git --release --verbose

      #fetch the internal name from the zip name (the technical name from the extension composer.json)
    - EXT_INTERNAL_NAME=$(ls | grep -e "$EXT_INTERNAL_NAME_PATTERN" | head -1)
    - EXT_INTERNAL_NAME=${EXT_INTERNAL_NAME/$EXT_INTERNAL_NAME_PATTERN/}

      #unzip the package, we need the raw files for our artifact
    - unzip $EXT_INTERNAL_NAME-package.zip

      # remove everything we don't want in our artifact
    - find . -not -name $EXT_INTERNAL_NAME -maxdepth 1 -exec rm -r {} \;

Todos for 0.1.0

This tool will be first an replacement for https://github.com/FriendsOfShopware/FroshPluginUploader

suggested commands

Login

  • account login - Login in your Shopware Account
  • account login - Logout from your ShopwareAccount

Companies

  • account company list - List all possible companies
  • account company use - Switch company and save it in config

Producer

  • account producer info - List producer information
  • account producer extension list - List all extensions per section: SW5, SW6, Apps
  • account producer extension create - Create a new extension
  • account producer extension delete - Delete a extension
  • account producer extension update - Update extension page by configuration
  • account producer extension upload - Upload extension update

Extension

  • extension prepare - Prepare a zip of the extension
  • extension zip - Create a zip of the extension
  • extension validate - Validate a Zip or folder
    • php syntax check
    • composer json checks
    • theme json validator
    • manifest validator

Version constraint ^6.4.0 in store sync

PHP Version

No response

Shopware Version

No response

Actual behaviour

Selects just 6.4.0.0 in the account as supported version

Expected behaviour

Selects every available version from 6.4.0.0 to 7.0.0.0

Steps to Reproduce?

Use the constraint for store release

Option to ignore untrusted certificates

Please describe the feature you would like to see implemented.

In my setup I use devenv with Caddy.
The problem I encountered is that Caddy can't install it's certificate due to permission issues inside devenv up (can't run sudo in non-interactive shell).

This results in the following error if I use shopware-cli project admin-api:

FATA[0000] Post "https://127.0.0.1:8000/api/oauth/token": x509: “Caddy Local Authority - ECC Intermediate” certificate is not trusted

It would be nice to have a flag/option to ignore this behavior.

Extension root is not correctly determined on apps

PHP Version

No response

Shopware Version

No response

Actual behaviour

It searches for src/Resources/app/storefront/src

Expected behaviour

But should do Resources/app/storefront/src

Steps to Reproduce?

Try an app

npm install in general source folder

Please describe the feature you would like to see implemented.

for _, ext := range assetCfg {
_, adminPathPackage := os.Stat(fmt.Sprintf("%s/%s/%s/package.json", projectRoot, ext.BasePath, filepath.Dir(ext.Administration.Path)))
_, adminPathNodeModules := os.Stat(fmt.Sprintf("%s/%s/%s/node_modules", projectRoot, ext.BasePath, filepath.Dir(ext.Administration.Path)))
_, storefrontPathPackage := os.Stat(fmt.Sprintf("%s/%s/%s/package.json", projectRoot, ext.BasePath, filepath.Dir(ext.Storefront.Path)))
_, storefrontPathNodeModules := os.Stat(fmt.Sprintf("%s/%s/%s/node_modules", projectRoot, ext.BasePath, filepath.Dir(ext.Storefront.Path)))
if ext.Administration.EntryFilePath != nil && adminPathPackage == nil && (os.IsNotExist(adminPathNodeModules) || forceNpmInstall) {
if err := runSimpleCommand(projectRoot, "npm", "install", "--prefix", fmt.Sprintf("%s/%s/%s", projectRoot, ext.BasePath, filepath.Dir(ext.Administration.Path)), "--no-save"); err != nil {
return err
}
}
if ext.Storefront.EntryFilePath != nil && storefrontPathPackage == nil && (os.IsNotExist(storefrontPathNodeModules) || forceNpmInstall) {
if err := runSimpleCommand(projectRoot, "npm", "install", "--prefix", fmt.Sprintf("%s/%s/%s", projectRoot, ext.BasePath, filepath.Dir(ext.Storefront.Path)), "--no-save"); err != nil {
return err
}
}
}

src/Resources/app/package.json should be installed, too.
People are using this folder to have changed modules in admin and storefront, f.e.

account login with saved old password

PHP Version

No response

Shopware Version

No response

Actual behaviour

When having logged in with a old password and want to call login again, the cli detects saved password. also it detects the password is wrong.

Expected behaviour

The cli should call relogging when saved password is wrong.
Additionally: remove shopware-api-client-token.json, too on every login.

Steps to Reproduce?

  • call shopware-cli account login.
  • change password of account
  • call shopware-cli account login again

validate: Ensure running in the correct PHP version / multiple versions

Please describe the feature you would like to see implemented.

I think extensions for 6.4 should be compatible with PHP7.4 - 8.1.

I was running a validate on 8.0 but it failed in the store which seems to check with PHP7.4.

It would be nice if the CLI uses different PHP versions for validation or shows a message, that you should use a different PHP runtime.

What do you think?

Remove package github.com/pkg/errors

Please describe the feature you would like to see implemented.

This package is archived, because there is no need for it, since you can wrap errors with fmt.Errorf(".... %w", err). Since Go1.20, you are also able to wrap multiple errors or use errors.Join(err1, err2, ...) from the stdlib.

Both methods can be checked with errors.Is() and errors.As().

Change command to shopware-cli

Please describe the feature you would like to see implemented.

As discussed, there could be some reasons to use command shopware-cli instead of shopware:

  • the project is told shopware-cli
  • It could suggest that you are in a shopware installation
  • ...

Building the store in the ci without DB ignores extensions

PHP Version

8.1

Shopware Version

6.4.18.1

Actual behaviour

The extensions are not build when no database connection is available.

Currently I run the following command in the ci:

 ## Compile
 compile:
   stage: compile
   image:
     name: ghcr.io/friendsofshopware/shopware-cli
     entrypoint: [ "/usr/local/bin/entrypoint.sh" ]
   script:
     - shopware-cli project admin-build

The following output:

 $ shopware-cli project admin-build
 time="2023-02-06T19:36:05Z" level=info msg="Building Administration in root /builds/liebscher-bracht/shop6.liebscher-bracht.com"
 Warning: Failed to load plugins. Message: An exception occurred in driver: SQLSTATE[HY000] [2002] Connection refused
 Warning: Failed to load apps. Loading apps from local. Message: An exception occurred in driver: SQLSTATE[HY000] [2002] Connection refused
  [OK] Dumped plugin configuration. 

Unfortunately the extensions are not buildt.

The same happens when I build the storefront

Expected behaviour

Expected to build the whole store with all extension without a db connection.

Steps to Reproduce?

Tried the CI=1 environment. Talk with @shyim on slack about it. He labeled it as a bug.

Remove secret when packing an app

Please describe the feature you would like to see implemented.

As mentioned in the docs you should never publish the app-secret. I'm wondering if it's a good idea to automatically remove the <secret> tag in the manifest.xml file when packing an app?

Before packing

<setup>
        <registrationUrl>https://my.example.com/registration</registrationUrl>
        <secret>xxxxx-xxxxx-xxxxx-xxxxx</secret>
</setup>

After packing

<setup>
        <registrationUrl>https://my.example.com/registration</registrationUrl>
</setup>

Reference: https://developer.shopware.com/docs/guides/plugins/apps/app-base-guide#registration-response
image

Config Sync

Please describe the feature you would like to see implemented.

  • System Config
  • Theme Config
  • Mail Template
  • Entity Sync
  • Custom Field Sets
  • Flow Builder
  • Rules
  • CMS

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Branch Automerge

These updates await pending status checks before automerging. Click on a checkbox to abort the branch automerge, and create a PR instead.

  • fix(deps): update all dependencies (github.com/evanw/esbuild, github.com/yuin/goldmark)

Detected dependencies

dockerfile
Dockerfile
Dockerfile.base
  • composer/composer 2-bin
github-actions
.github/workflows/base-docker.yml
  • actions/checkout v3
  • docker/setup-qemu-action v2
  • docker/setup-buildx-action v2
  • docker/build-push-action v4
.github/workflows/codeql.yml
  • actions/checkout v3
  • github/codeql-action v2
  • github/codeql-action v2
  • github/codeql-action v2
.github/workflows/config-schema-update.yml
  • actions/checkout v3
.github/workflows/go_test.yml
  • actions/checkout v3
  • actions/setup-go v4
.github/workflows/lint.yml
  • actions/checkout v3
  • actions/setup-go v4
  • golangci/golangci-lint-action v3
.github/workflows/qodana.yml
  • actions/checkout v3
.github/workflows/release.yml
  • actions/checkout v3
  • actions/setup-go v4
  • docker/setup-buildx-action v2
  • sigstore/cosign-installer v3
  • anchore/sbom-action v0.14.3
  • goreleaser/goreleaser-action v4
gomod
go.mod
  • go 1.20
  • github.com/bep/godartsass/v2 v2.0.0
  • github.com/caarlos0/env/v9 v9.0.0
  • github.com/doutorfinancas/go-mad v0.0.0-20230320131904-348560be9c36@348560be9c36
  • github.com/evanw/esbuild v0.18.15
  • github.com/friendsofshopware/go-shopware-admin-api-sdk v0.0.0-20230318202833-6328f419267d@6328f419267d
  • github.com/google/uuid v1.3.0
  • github.com/gorilla/schema v1.2.0
  • github.com/manifoldco/promptui v0.9.0
  • github.com/microcosm-cc/bluemonday v1.0.25
  • github.com/olekukonko/tablewriter v0.0.5
  • github.com/otiai10/copy v1.12.0
  • github.com/sashabaranov/go-openai v1.14.1
  • github.com/spf13/cobra v1.7.0
  • github.com/stretchr/testify v1.8.4
  • github.com/vulcand/oxy/v2 v2.0.0-20230427132221-be5cf38f3c1c@be5cf38f3c1c
  • github.com/yuin/goldmark v1.5.4
  • go.uber.org/zap v1.24.0
  • gopkg.in/yaml.v3 v3.0.1
  • dario.cat/mergo v1.0.0
  • github.com/NYTimes/gziphandler v1.1.1
  • golang.org/x/net v0.12.0
pip_requirements
wiki/requirements.txt

  • Check this box to trigger a request for Renovate to run again on this repository

Command to get composer bearer key

Please describe the feature you would like to see implemented.

I'd like to have a command to get/create bearer for packages.shopware.com

docker php-version

Please describe the feature you would like to see implemented.

Minimum PHP version of shopware is 7.4.
Running "extension prepare" on plugin uses PHP 8.0, which can result in errors while components are installed which are incompatible.

Should we set config.platform.php in composer.json to 7.4?

[project dump] Tablenames in uppercase letters can't be ignored

PHP Version

8.0

Shopware Version

6.4.12.0

Actual behaviour

We have tables in our SW6 database called "SW5_*", e.g. "SW5_s_articles_attributes" which should be ignored when dumping. But they are dumped even if written in .shopware-project.yaml under ignore config.

Expected behaviour

All tables under ignore config should be ignored when dumping (even the ones with uppercase table names)

Steps to Reproduce?

  • create a table named "SW5_s_articles_attributes" in your database (with some data rows)
  • add it to your .shopware-project.yaml:
dump:
    ignore:
        - SW5_s_articles_attributes
  • create a dump

ESBuild doesn't work if using core services

PHP Version

No response

Shopware Version

No response

Actual behaviour

If using services or classes from the Shopware core the compilation doesn't work.
According to the documentation e.g. import Plugin from 'src/plugin-system/plugin.class'; already causes this error.

shopware-cli extension build custom/static-plugins/shopware-platform-delivery-time/

up to date, audited 2 packages in 5s

found 0 vulnerabilities
npm notice 
npm notice New major version of npm available! 8.19.2 -> 9.1.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.1.2
npm notice Run npm install -g [email protected] to update!
npm notice 
INFO[0004] Downloading dart-sass                        
INFO[0005] Using dart-sass binary /root/.cache/dart-sass-embedded/dart-sass-embedded 

  extension.js   126.4kb
  extension.css   21.0kb

⚡ Done in 602ms
INFO[0005] Using dart-sass binary /root/.cache/dart-sass-embedded/dart-sass-embedded 
✘ [ERROR] Could not resolve "src/plugin-system/plugin.class"

    custom/static-plugins/shopware-platform-delivery-time/src/Resources/app/storefront/src/deliveryDate/deliveryDate.plugin.js:5:19:
      5 │ import Plugin from 'src/plugin-system/plugin.class';
        ╵                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  You can mark the path "src/plugin-system/plugin.class" as external to exclude it from the bundle,
  which will remove this error.

✘ [ERROR] Could not resolve "src/service/http-client.service"

    custom/static-plugins/shopware-platform-delivery-time/src/Resources/app/storefront/src/deliveryDate/deliveryDateTime.js:1:23:
      1 │ import HttpClient from 'src/service/http-client.service';
        ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  You can mark the path "src/service/http-client.service" as external to exclude it from the bundle,
  which will remove this error.

2 errors

Expected behaviour

It should compile

Steps to Reproduce?

build:
  zip:
    composer:
      enabled: true
    assets:
      enabled: false
      enable_es_build_for_admin: true
      enable_es_build_for_storefront: true
    pack:
      excludes:
        paths:
          - .cache
          - .editorconfig
          - .gitignore
          - .idea
docker run --rm -ti -v $PWD:/tmp/build -w /tmp/build --entrypoint= ghcr.io/friendsofshopware/shopware-cli:0.1.44 bash
shopware-cli extension build custom/static-plugins/shopware-platform-delivery-time/

Add stateless asset building

Please describe the feature you would like to see implemented.

  • Clone platform to temp dir with depth 1
  • Generate var/plugin.json based on Extension
  • Build Admin Assets
  • Build Storefront Assets

This should be disable able using .shopware-extension.yml

Watcher breaks when it bumps on a ~scss/variables import

PHP Version

8.0.0

Shopware Version

6.4.11.1

Actual behaviour

Tested the watcher on a plugin with the ~scss/variables import:

file: "_file_.scss", context: "@import \"~scss/variables\";\n": Can't find stylesheet to import.

This import is used for using the variables in Shopping Experience blocks (previews).

Expected behaviour

The import is recognised by the watcher and compiles without breaking

Steps to Reproduce?

shopware-cli extension admin-watch _PluginDirectory_ http://localhost

Tested the watcher on a plugin that includes an scss file with a ~scss/variables import

Zipping extensions fails when installing dart-sass

PHP Version

No response

Shopware Version

No response

Actual behaviour

I run shopware-cli extension zip /path/to/extension --disable-git

I get

INFO[0001] Downloading dart-sass                        
INFO[0001] Using dart-sass binary /root/.cache/dart-sass-embedded/dart-sass-embedded 
FATA[0001] close |0: file already closed      

Expected behaviour

Build

Steps to Reproduce?

See actual behavior

NPM executable file not found in $PATH

PHP Version

8.1

Shopware Version

6.4.20

Actual behaviour

Running package in our GitLab CI with Docker.
Package fails with building assets: exec: \"npm\": executable file not found in $PATH

Executing "step_script" stage of the job script 00:09
Using docker image sha256:45cbf57a5c858edc1d07d38fb50d4efe17ba532584a20769ea3c7c713ef7f664 for ghcr.io/friendsofshopware/shopware-cli:v0.1-phpv8.1 with digest ghcr.io/friendsofshopware/shopware-cli@sha256:7c29a5043e58e3aa7e56bf2543b6f4264238da4df3020710a67db84702f03bc0 ...
$ shopware-cli --version
shopware-cli version 0.1.54
$ shopware-cli extension zip ./ package --release --verbose
No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Writing lock file
Installing dependencies from lock file
Nothing to install, update or remove
Generating optimized autoload files
Cloning into '/tmp/extension2478198386'...
Updating files: 100% (17171/17171), done.
Usage:
  shopware-cli extension zip [path] [branch] [flags]
Flags:
      --disable-git   Use the source folder as it is
  -h, --help          help for zip
      --release       Release mode (remove app secrets)
Global Flags:
      --config string   config file (default is $HOME/.shopware-cli.yaml)
      --verbose         show debug output
time="2023-03-08T14:50:21Z" level=fatal msg="building assets: exec: \"npm\": executable file not found in $PATH"

Expected behaviour

The docker image would provide the required npm

Steps to Reproduce?

gitlab-ci.yml

build:package:
  image:
    name: ghcr.io/friendsofshopware/shopware-cli:v0.1-phpv8.1
    entrypoint: [""]
  tags:
    - docker
  variables:
    FILE_NAME: $BASE_FILE_NAME.zip
    EXT_INTERNAL_NAME_PATTERN: -package.zip
  artifacts:
    name: $BASE_FILE_NAME
    paths:
      - "*"
  stage: build
  script:
    - shopware-cli --version
      #package the extension (executes prepare, build & zip)
    - shopware-cli extension zip ./ package --release --verbose

[project dump] Triggers are not dumped

PHP Version

8.0

Shopware Version

6.4.12.0

Actual behaviour

When dumping a SW6 database, the triggers present in the database are not in the resulting dump.sql.

Expected behaviour

Triggers should also be dumped to dump.sql

Steps to Reproduce?

  • create a trigger in your database
  • dump the database

Add a way to find easily the latest release

Please describe the feature you would like to see implemented.

Hi,

For automation purposes, we would very much like a sort of latest tag.

Now we need to manually pick a version here: https://github.com/FriendsOfShopware/shopware-cli/releases/

It would be nice to have something available like:

https://github.com/FriendsOfShopware/shopware-cli/releases/download/latest/shopware-cli_latest_linux_amd64.deb

Any other means to find the latest release are welcome :)

shopware-cli project extension list 'fatal error'

PHP Version

7.4.32

Shopware Version

6.4.16.0

Actual behaviour

command shopware-cli project extension list --project-config .shopware-project.dev.yml return error

FATA[0001] API request failed, got http code 500 with content: Shopware\Core\Framework\Api\Context\AdminApiSource does not have a valid user ID

from app log

[2022-10-11T11:57:09.914365+00:00] request.CRITICAL: Uncaught PHP Exception Shopware\Core\Framework\Api\Context\Exception\InvalidContextSourceUserException: "Shopware\Core\Framework\Api\Context\AdminApiSource does not have a valid user ID" at /var/www/html/vendor/shopware/core/Framework/Store/Authentication/StoreRequestOptionsProvider.php line 97 {"exception":"[object] (Shopware\\Core\\Framework\\Api\\Context\\Exception\\InvalidContextSourceUserException(code: 0): Shopware\\Core\\Framework\\Api\\Context\\AdminApiSource does not have a valid user ID at /var/www/html/vendor/shopware/core/Framework/Store/Authentication/StoreRequestOptionsProvider.php:97)"} []

Expected behaviour

get list of plugins

Steps to Reproduce?

run shopware-cli project extension list

Icon must be in repo

Please describe the feature you would like to see implemented.

Shopware extension store complains about missing icon, it would be cool if the CLI tool already did that.

extra.plugin-icon#missing: missing plugin icon, it must be located under "src/Resources/config/plugin.png", or a custom path defined in "extra"."plugin-icon"

docker

PHP Version

No response

Shopware Version

No response

Actual behaviour

docker run --rm -v ${PWD}:/app ghcr.io/friendsofshopware/shopware-cli extension prepare /app

results in Error: level=fatal msg="prepare zip: PrepareFolderForZipping: exec: \"composer\": executable file not found in $PATH"

Expected behaviour

should work

Steps to Reproduce?

call command in plugin

Migrate to Zap Logger

Currently used Logrus is in maintenance mode only. So we should switch to Zap logger.

Zap is already in the dependencies so it should be convenient to switch

  • #127
  • Test Basic Store Stuff
  • More Context everywhere to first argument

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.