You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
rm -rf command described in the "Change to developer mode" section shows absolute paths
Description:
it seems highly unlikely (if even possible) that someone's magento root would be the same as their actual system root directory, which is where the current recommended rm -rf command (for use before switching to developer mode from production mode) suggests the files to be deleted live.
or as a variable example, rather than a command someone might copy-paste:
rm -rf <magento_root>/generated/metadata/* <magento_root>/generated/code/*
Additional information:
might be worth looking back to earlier versions (same issue exists on the 2.2 version instructions as well, the 2.1 version instructions were for different directories, but did at least specify the <magento_root>)
The text was updated successfully, but these errors were encountered:
General issue
rm -rf command described in the "Change to developer mode" section shows absolute paths
Description:
it seems highly unlikely (if even possible) that someone's magento root would be the same as their actual system root directory, which is where the current recommended rm -rf command (for use before switching to developer mode from production mode) suggests the files to be deleted live.
Possible solutions:
change
rm -rf /generated/metadata/* /generated/code/*
to
rm -rf generated/metadata/* generated/code/*
or as a variable example, rather than a command someone might copy-paste:
rm -rf <magento_root>/generated/metadata/* <magento_root>/generated/code/*
Additional information:
might be worth looking back to earlier versions (same issue exists on the 2.2 version instructions as well, the 2.1 version instructions were for different directories, but did at least specify the <magento_root>)
The text was updated successfully, but these errors were encountered: