We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
According to #138, especially #138 (comment), you should be able to run the Magepack generate and bundle command with a shortcut.
generate
bundle
Long: warden env exec magepack magepack generate [...] Short: warden env exec magepack generate [...]
warden env exec magepack magepack generate [...]
warden env exec magepack generate [...]
Long: warden env exec magepack magepack bundle Short: warden env exec magepack bundle
warden env exec magepack magepack bundle
warden env exec magepack bundle
However, this does not seem to work. For me, only the long version works.
Looking at https://github.com/wardenenv/images/blob/7fb6d1c3e52d55da356b568f50b8a7c494fe21b2/magepack/bin/generate.sh / https://github.com/wardenenv/images/blob/7fb6d1c3e52d55da356b568f50b8a7c494fe21b2/magepack/bin/bundle.sh, the commands try to execute /usr/bin/magepack. However, warden env exec magepack which magepack gives me /usr/local/bin/magepack. Hence, I think the path to the magepack executable simply needs to be fixed. If anyone would shortly verify my findings, I am happy to send a PR.
/usr/bin/magepack
warden env exec magepack which magepack
/usr/local/bin/magepack
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
According to #138, especially #138 (comment), you should be able to run the Magepack
generate
andbundle
command with a shortcut.Long:
warden env exec magepack magepack generate [...]
Short:
warden env exec magepack generate [...]
Long:
warden env exec magepack magepack bundle
Short:
warden env exec magepack bundle
However, this does not seem to work. For me, only the long version works.
Looking at https://github.com/wardenenv/images/blob/7fb6d1c3e52d55da356b568f50b8a7c494fe21b2/magepack/bin/generate.sh / https://github.com/wardenenv/images/blob/7fb6d1c3e52d55da356b568f50b8a7c494fe21b2/magepack/bin/bundle.sh, the commands try to execute
/usr/bin/magepack
. However,warden env exec magepack which magepack
gives me/usr/local/bin/magepack
. Hence, I think the path to the magepack executable simply needs to be fixed. If anyone would shortly verify my findings, I am happy to send a PR.The text was updated successfully, but these errors were encountered: