Magento2 which command Run and when to RunMagento 2: What is difference between Cache Clean & Cache Flush?setup:static-content:deploy need to run for minor php changes?How to add custom css in luma theme in magento 2.1.2Magento 2 Module upgrade errorWhen to run following commands in magento2?Magento 2: Static files are present but shows 404Why do i have to always run the commands to clean cache in Magento 2.1.8?How to customize css in pub/static folder. Automatically update old css in magento 2Magento 2: Magento UI is not working properly. After deleting all productsWhen using Magento 2 the admin panel buttons are un-responsiveCan Anyone explain in details that how magento2 cache working?
Single word to change groups
What kind of footwear is suitable for walking in micro gravity environment?
What is the difference between something being completely legal and being completely decriminalized?
Imaginary part of expression too difficult to calculate
"Marked down as someone wanting to sell shares." What does that mean?
PTIJ: Which Dr. Seuss books should one obtain?
Error in master's thesis, I do not know what to do
How to balance a monster modification (zombie)?
Why didn’t Eve recognize the little cockroach as a living organism?
What (if any) is the reason to buy in small local stores?
How to find the largest number(s) in a list of elements, possibly non-unique?
Does convergence of polynomials imply that of its coefficients?
Why doesn't the fusion process of the sun speed up?
Can other pieces capture a threatening piece and prevent a checkmate?
When should a starting writer get his own webpage?
What is the tangent at a sharp point on a curve?
Weird lines in Microsoft Word
The English Debate
What favor did Moody owe Dumbledore?
Have any astronauts/cosmonauts died in space?
How to test the sharpness of a knife?
Symbolism of 18 Journeyers
Animating wave motion in water
How do you justify more code being written by following clean code practices?
Magento2 which command Run and when to Run
Magento 2: What is difference between Cache Clean & Cache Flush?setup:static-content:deploy need to run for minor php changes?How to add custom css in luma theme in magento 2.1.2Magento 2 Module upgrade errorWhen to run following commands in magento2?Magento 2: Static files are present but shows 404Why do i have to always run the commands to clean cache in Magento 2.1.8?How to customize css in pub/static folder. Automatically update old css in magento 2Magento 2: Magento UI is not working properly. After deleting all productsWhen using Magento 2 the admin panel buttons are un-responsiveCan Anyone explain in details that how magento2 cache working?
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
and when they need to Run . which tasks Output to need cache:flush or clean ** and which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
I consume 4 to 5 min to run cache:flush,upgrade and deploy.
magento2 cache cli setup-di-compile dicompilation
add a comment |
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
and when they need to Run . which tasks Output to need cache:flush or clean ** and which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
I consume 4 to 5 min to run cache:flush,upgrade and deploy.
magento2 cache cli setup-di-compile dicompilation
1
You can find the awnser in this thread: magento.stackexchange.com/questions/138155/…
– Stijn CompactCode
Feb 26 at 17:10
add a comment |
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
and when they need to Run . which tasks Output to need cache:flush or clean ** and which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
I consume 4 to 5 min to run cache:flush,upgrade and deploy.
magento2 cache cli setup-di-compile dicompilation
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
and when they need to Run . which tasks Output to need cache:flush or clean ** and which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
I consume 4 to 5 min to run cache:flush,upgrade and deploy.
magento2 cache cli setup-di-compile dicompilation
magento2 cache cli setup-di-compile dicompilation
edited 22 mins ago
Shoaib Munir
2,1101828
2,1101828
asked Feb 26 at 17:08
HaFiz UmerHaFiz Umer
3339
3339
1
You can find the awnser in this thread: magento.stackexchange.com/questions/138155/…
– Stijn CompactCode
Feb 26 at 17:10
add a comment |
1
You can find the awnser in this thread: magento.stackexchange.com/questions/138155/…
– Stijn CompactCode
Feb 26 at 17:10
1
1
You can find the awnser in this thread: magento.stackexchange.com/questions/138155/…
– Stijn CompactCode
Feb 26 at 17:10
You can find the awnser in this thread: magento.stackexchange.com/questions/138155/…
– Stijn CompactCode
Feb 26 at 17:10
add a comment |
3 Answers
3
active
oldest
votes
Although question have already been answered and accepted as well, but i thought it would be nice to compile all points in single answer for better understanding and for other users who are searching for such understanding:
So we will go part by part of question(s):
Question Part A :
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
as @Shoib Answers, cache:flush destroys the cache storage and build cache again where as cache:clean cleans the cache and doesn't destroy the storage.
Question Part B :
which tasks Output to need cache:flush or clean
when to Cache Clean ?
When you make any change in template, layout or configurations , only clean cache, you should avoid cache:flush in any case. 90% your frontend , configuration issues will be solved by cache:clean.
HINT :
During frontend theme development, you can enable all caches just disable full_page cache
, this will save you lot of time and in development, you just need to run cache:clean command.
When to Cache Flush ?
Cache flush only and only , if your desired changes not worked as expected after cache:clean command.
Question Part C :
which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
In part c of your question, you mentioned commands like :
1 - **di:compile** , 2 - **setup:upgrade** , 3 - **setup:static-content:deploy**
Let's re-order these as per usage and recommendation of commands :
1 - setup:upgrade
2 - di:compile
3 - setup:static-content:deploy
1 - setup:upgrade :
When you add new module you should run this command this command will add your module entry in setup_module table and also in config.php file. As it updates the Database schema.
2 - setup:di:compile
This command is used to create factories, proxies, interceptors etc :
- Application code generation (factories, proxies, and so on)
- Area configuration aggregation (that is, optimized dependency injection configurations per area)
- Interceptor generation (that is, optimized code generation of interceptors)
- Interception cache generation
- Repositories code generation (that is, generated code for APIs)
- Service data attributes generation (that is, generated extension classes for data objects)
in short run this command when you make any change in your module classes files, constructor etc and generates the contents of the var/di folder in Magento <2.2
and generated for Magento >= 2.2
.
Refer to Magento Dev Docs for complete detail
3 - setup:static-content:deploy
Run this command when you are developing / making changes in your theme LESS or other JS / static files. Static view files are located in the /pub/static directory, and some are cached in the /var/view_preprocessed directory as well.
For more details about static content refer to Magento Dev Docs here and you can also read in which mode you should run which command.
Note :
If you make any change in template or layout file, php bin/magento cache:clean command will work for you , you don't need to deploy static content.
Hope this will help to understand mechanism.
add a comment |
Cleaning a cache type deletes all items from enabled Magento cache types only. In other words, this option does not affect other processes or applications because it cleans only the cache that Magento uses.
Flushing a cache type purges the cache storage, which might affect other processes applications that are using the same storage.
In short: Clean is a soft way of cleaning cache whereas flush is the hard flush of cache storage.
Reference: https://devdocs.magento.com/guides/v2.3/config-guide/cli/config-cli-subcommands-cache.html
Magento 2: What is difference between Cache Clean & Cache Flush?
what mean of which might affect other processes applications that are using the same storage ? which other process ?
– HaFiz Umer
Feb 27 at 6:52
1
Like third-party developers can put any data in any segment of the cache. They can use your cache storage. So, when you clean, it will not effect anything, whereas if you flush cache it will also flush third party module's cache. Then that module will regenerate cache in cache storage
– Shoaib Munir
Feb 27 at 7:01
yes clean ! third-pary modules .
– HaFiz Umer
Feb 27 at 7:03
when setup:di:compile run then why need to run also cache:flush and also upgrade,deploy
– HaFiz Umer
Feb 27 at 7:11
@HaFizUmer see answer that Muhammad Ahmed has given, he described when to run other commands
– Shoaib Munir
Feb 27 at 16:53
add a comment |
di:compile
=>This command is used when you make change in di file or create new plugin or preference.
setup:upgrade
=>This command is used when you make a new module and you want to used it in your magento project.
indexer:indexer
=>When you make a change on frontend then you need to use this command.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f263524%2fmagento2-which-command-run-and-when-to-run%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Although question have already been answered and accepted as well, but i thought it would be nice to compile all points in single answer for better understanding and for other users who are searching for such understanding:
So we will go part by part of question(s):
Question Part A :
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
as @Shoib Answers, cache:flush destroys the cache storage and build cache again where as cache:clean cleans the cache and doesn't destroy the storage.
Question Part B :
which tasks Output to need cache:flush or clean
when to Cache Clean ?
When you make any change in template, layout or configurations , only clean cache, you should avoid cache:flush in any case. 90% your frontend , configuration issues will be solved by cache:clean.
HINT :
During frontend theme development, you can enable all caches just disable full_page cache
, this will save you lot of time and in development, you just need to run cache:clean command.
When to Cache Flush ?
Cache flush only and only , if your desired changes not worked as expected after cache:clean command.
Question Part C :
which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
In part c of your question, you mentioned commands like :
1 - **di:compile** , 2 - **setup:upgrade** , 3 - **setup:static-content:deploy**
Let's re-order these as per usage and recommendation of commands :
1 - setup:upgrade
2 - di:compile
3 - setup:static-content:deploy
1 - setup:upgrade :
When you add new module you should run this command this command will add your module entry in setup_module table and also in config.php file. As it updates the Database schema.
2 - setup:di:compile
This command is used to create factories, proxies, interceptors etc :
- Application code generation (factories, proxies, and so on)
- Area configuration aggregation (that is, optimized dependency injection configurations per area)
- Interceptor generation (that is, optimized code generation of interceptors)
- Interception cache generation
- Repositories code generation (that is, generated code for APIs)
- Service data attributes generation (that is, generated extension classes for data objects)
in short run this command when you make any change in your module classes files, constructor etc and generates the contents of the var/di folder in Magento <2.2
and generated for Magento >= 2.2
.
Refer to Magento Dev Docs for complete detail
3 - setup:static-content:deploy
Run this command when you are developing / making changes in your theme LESS or other JS / static files. Static view files are located in the /pub/static directory, and some are cached in the /var/view_preprocessed directory as well.
For more details about static content refer to Magento Dev Docs here and you can also read in which mode you should run which command.
Note :
If you make any change in template or layout file, php bin/magento cache:clean command will work for you , you don't need to deploy static content.
Hope this will help to understand mechanism.
add a comment |
Although question have already been answered and accepted as well, but i thought it would be nice to compile all points in single answer for better understanding and for other users who are searching for such understanding:
So we will go part by part of question(s):
Question Part A :
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
as @Shoib Answers, cache:flush destroys the cache storage and build cache again where as cache:clean cleans the cache and doesn't destroy the storage.
Question Part B :
which tasks Output to need cache:flush or clean
when to Cache Clean ?
When you make any change in template, layout or configurations , only clean cache, you should avoid cache:flush in any case. 90% your frontend , configuration issues will be solved by cache:clean.
HINT :
During frontend theme development, you can enable all caches just disable full_page cache
, this will save you lot of time and in development, you just need to run cache:clean command.
When to Cache Flush ?
Cache flush only and only , if your desired changes not worked as expected after cache:clean command.
Question Part C :
which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
In part c of your question, you mentioned commands like :
1 - **di:compile** , 2 - **setup:upgrade** , 3 - **setup:static-content:deploy**
Let's re-order these as per usage and recommendation of commands :
1 - setup:upgrade
2 - di:compile
3 - setup:static-content:deploy
1 - setup:upgrade :
When you add new module you should run this command this command will add your module entry in setup_module table and also in config.php file. As it updates the Database schema.
2 - setup:di:compile
This command is used to create factories, proxies, interceptors etc :
- Application code generation (factories, proxies, and so on)
- Area configuration aggregation (that is, optimized dependency injection configurations per area)
- Interceptor generation (that is, optimized code generation of interceptors)
- Interception cache generation
- Repositories code generation (that is, generated code for APIs)
- Service data attributes generation (that is, generated extension classes for data objects)
in short run this command when you make any change in your module classes files, constructor etc and generates the contents of the var/di folder in Magento <2.2
and generated for Magento >= 2.2
.
Refer to Magento Dev Docs for complete detail
3 - setup:static-content:deploy
Run this command when you are developing / making changes in your theme LESS or other JS / static files. Static view files are located in the /pub/static directory, and some are cached in the /var/view_preprocessed directory as well.
For more details about static content refer to Magento Dev Docs here and you can also read in which mode you should run which command.
Note :
If you make any change in template or layout file, php bin/magento cache:clean command will work for you , you don't need to deploy static content.
Hope this will help to understand mechanism.
add a comment |
Although question have already been answered and accepted as well, but i thought it would be nice to compile all points in single answer for better understanding and for other users who are searching for such understanding:
So we will go part by part of question(s):
Question Part A :
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
as @Shoib Answers, cache:flush destroys the cache storage and build cache again where as cache:clean cleans the cache and doesn't destroy the storage.
Question Part B :
which tasks Output to need cache:flush or clean
when to Cache Clean ?
When you make any change in template, layout or configurations , only clean cache, you should avoid cache:flush in any case. 90% your frontend , configuration issues will be solved by cache:clean.
HINT :
During frontend theme development, you can enable all caches just disable full_page cache
, this will save you lot of time and in development, you just need to run cache:clean command.
When to Cache Flush ?
Cache flush only and only , if your desired changes not worked as expected after cache:clean command.
Question Part C :
which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
In part c of your question, you mentioned commands like :
1 - **di:compile** , 2 - **setup:upgrade** , 3 - **setup:static-content:deploy**
Let's re-order these as per usage and recommendation of commands :
1 - setup:upgrade
2 - di:compile
3 - setup:static-content:deploy
1 - setup:upgrade :
When you add new module you should run this command this command will add your module entry in setup_module table and also in config.php file. As it updates the Database schema.
2 - setup:di:compile
This command is used to create factories, proxies, interceptors etc :
- Application code generation (factories, proxies, and so on)
- Area configuration aggregation (that is, optimized dependency injection configurations per area)
- Interceptor generation (that is, optimized code generation of interceptors)
- Interception cache generation
- Repositories code generation (that is, generated code for APIs)
- Service data attributes generation (that is, generated extension classes for data objects)
in short run this command when you make any change in your module classes files, constructor etc and generates the contents of the var/di folder in Magento <2.2
and generated for Magento >= 2.2
.
Refer to Magento Dev Docs for complete detail
3 - setup:static-content:deploy
Run this command when you are developing / making changes in your theme LESS or other JS / static files. Static view files are located in the /pub/static directory, and some are cached in the /var/view_preprocessed directory as well.
For more details about static content refer to Magento Dev Docs here and you can also read in which mode you should run which command.
Note :
If you make any change in template or layout file, php bin/magento cache:clean command will work for you , you don't need to deploy static content.
Hope this will help to understand mechanism.
Although question have already been answered and accepted as well, but i thought it would be nice to compile all points in single answer for better understanding and for other users who are searching for such understanding:
So we will go part by part of question(s):
Question Part A :
Kindly Clear Difference Between php bin/magento cache:flush and cache:clean
as @Shoib Answers, cache:flush destroys the cache storage and build cache again where as cache:clean cleans the cache and doesn't destroy the storage.
Question Part B :
which tasks Output to need cache:flush or clean
when to Cache Clean ?
When you make any change in template, layout or configurations , only clean cache, you should avoid cache:flush in any case. 90% your frontend , configuration issues will be solved by cache:clean.
HINT :
During frontend theme development, you can enable all caches just disable full_page cache
, this will save you lot of time and in development, you just need to run cache:clean command.
When to Cache Flush ?
Cache flush only and only , if your desired changes not worked as expected after cache:clean command.
Question Part C :
which task need these Commands => **di:compile,setup:upgrade,setup:static-content:deploy
In part c of your question, you mentioned commands like :
1 - **di:compile** , 2 - **setup:upgrade** , 3 - **setup:static-content:deploy**
Let's re-order these as per usage and recommendation of commands :
1 - setup:upgrade
2 - di:compile
3 - setup:static-content:deploy
1 - setup:upgrade :
When you add new module you should run this command this command will add your module entry in setup_module table and also in config.php file. As it updates the Database schema.
2 - setup:di:compile
This command is used to create factories, proxies, interceptors etc :
- Application code generation (factories, proxies, and so on)
- Area configuration aggregation (that is, optimized dependency injection configurations per area)
- Interceptor generation (that is, optimized code generation of interceptors)
- Interception cache generation
- Repositories code generation (that is, generated code for APIs)
- Service data attributes generation (that is, generated extension classes for data objects)
in short run this command when you make any change in your module classes files, constructor etc and generates the contents of the var/di folder in Magento <2.2
and generated for Magento >= 2.2
.
Refer to Magento Dev Docs for complete detail
3 - setup:static-content:deploy
Run this command when you are developing / making changes in your theme LESS or other JS / static files. Static view files are located in the /pub/static directory, and some are cached in the /var/view_preprocessed directory as well.
For more details about static content refer to Magento Dev Docs here and you can also read in which mode you should run which command.
Note :
If you make any change in template or layout file, php bin/magento cache:clean command will work for you , you don't need to deploy static content.
Hope this will help to understand mechanism.
answered Mar 7 at 12:52
Naveed AsimNaveed Asim
2,7142317
2,7142317
add a comment |
add a comment |
Cleaning a cache type deletes all items from enabled Magento cache types only. In other words, this option does not affect other processes or applications because it cleans only the cache that Magento uses.
Flushing a cache type purges the cache storage, which might affect other processes applications that are using the same storage.
In short: Clean is a soft way of cleaning cache whereas flush is the hard flush of cache storage.
Reference: https://devdocs.magento.com/guides/v2.3/config-guide/cli/config-cli-subcommands-cache.html
Magento 2: What is difference between Cache Clean & Cache Flush?
what mean of which might affect other processes applications that are using the same storage ? which other process ?
– HaFiz Umer
Feb 27 at 6:52
1
Like third-party developers can put any data in any segment of the cache. They can use your cache storage. So, when you clean, it will not effect anything, whereas if you flush cache it will also flush third party module's cache. Then that module will regenerate cache in cache storage
– Shoaib Munir
Feb 27 at 7:01
yes clean ! third-pary modules .
– HaFiz Umer
Feb 27 at 7:03
when setup:di:compile run then why need to run also cache:flush and also upgrade,deploy
– HaFiz Umer
Feb 27 at 7:11
@HaFizUmer see answer that Muhammad Ahmed has given, he described when to run other commands
– Shoaib Munir
Feb 27 at 16:53
add a comment |
Cleaning a cache type deletes all items from enabled Magento cache types only. In other words, this option does not affect other processes or applications because it cleans only the cache that Magento uses.
Flushing a cache type purges the cache storage, which might affect other processes applications that are using the same storage.
In short: Clean is a soft way of cleaning cache whereas flush is the hard flush of cache storage.
Reference: https://devdocs.magento.com/guides/v2.3/config-guide/cli/config-cli-subcommands-cache.html
Magento 2: What is difference between Cache Clean & Cache Flush?
what mean of which might affect other processes applications that are using the same storage ? which other process ?
– HaFiz Umer
Feb 27 at 6:52
1
Like third-party developers can put any data in any segment of the cache. They can use your cache storage. So, when you clean, it will not effect anything, whereas if you flush cache it will also flush third party module's cache. Then that module will regenerate cache in cache storage
– Shoaib Munir
Feb 27 at 7:01
yes clean ! third-pary modules .
– HaFiz Umer
Feb 27 at 7:03
when setup:di:compile run then why need to run also cache:flush and also upgrade,deploy
– HaFiz Umer
Feb 27 at 7:11
@HaFizUmer see answer that Muhammad Ahmed has given, he described when to run other commands
– Shoaib Munir
Feb 27 at 16:53
add a comment |
Cleaning a cache type deletes all items from enabled Magento cache types only. In other words, this option does not affect other processes or applications because it cleans only the cache that Magento uses.
Flushing a cache type purges the cache storage, which might affect other processes applications that are using the same storage.
In short: Clean is a soft way of cleaning cache whereas flush is the hard flush of cache storage.
Reference: https://devdocs.magento.com/guides/v2.3/config-guide/cli/config-cli-subcommands-cache.html
Magento 2: What is difference between Cache Clean & Cache Flush?
Cleaning a cache type deletes all items from enabled Magento cache types only. In other words, this option does not affect other processes or applications because it cleans only the cache that Magento uses.
Flushing a cache type purges the cache storage, which might affect other processes applications that are using the same storage.
In short: Clean is a soft way of cleaning cache whereas flush is the hard flush of cache storage.
Reference: https://devdocs.magento.com/guides/v2.3/config-guide/cli/config-cli-subcommands-cache.html
Magento 2: What is difference between Cache Clean & Cache Flush?
edited Feb 26 at 17:34
answered Feb 26 at 17:26
Shoaib MunirShoaib Munir
2,1101828
2,1101828
what mean of which might affect other processes applications that are using the same storage ? which other process ?
– HaFiz Umer
Feb 27 at 6:52
1
Like third-party developers can put any data in any segment of the cache. They can use your cache storage. So, when you clean, it will not effect anything, whereas if you flush cache it will also flush third party module's cache. Then that module will regenerate cache in cache storage
– Shoaib Munir
Feb 27 at 7:01
yes clean ! third-pary modules .
– HaFiz Umer
Feb 27 at 7:03
when setup:di:compile run then why need to run also cache:flush and also upgrade,deploy
– HaFiz Umer
Feb 27 at 7:11
@HaFizUmer see answer that Muhammad Ahmed has given, he described when to run other commands
– Shoaib Munir
Feb 27 at 16:53
add a comment |
what mean of which might affect other processes applications that are using the same storage ? which other process ?
– HaFiz Umer
Feb 27 at 6:52
1
Like third-party developers can put any data in any segment of the cache. They can use your cache storage. So, when you clean, it will not effect anything, whereas if you flush cache it will also flush third party module's cache. Then that module will regenerate cache in cache storage
– Shoaib Munir
Feb 27 at 7:01
yes clean ! third-pary modules .
– HaFiz Umer
Feb 27 at 7:03
when setup:di:compile run then why need to run also cache:flush and also upgrade,deploy
– HaFiz Umer
Feb 27 at 7:11
@HaFizUmer see answer that Muhammad Ahmed has given, he described when to run other commands
– Shoaib Munir
Feb 27 at 16:53
what mean of which might affect other processes applications that are using the same storage ? which other process ?
– HaFiz Umer
Feb 27 at 6:52
what mean of which might affect other processes applications that are using the same storage ? which other process ?
– HaFiz Umer
Feb 27 at 6:52
1
1
Like third-party developers can put any data in any segment of the cache. They can use your cache storage. So, when you clean, it will not effect anything, whereas if you flush cache it will also flush third party module's cache. Then that module will regenerate cache in cache storage
– Shoaib Munir
Feb 27 at 7:01
Like third-party developers can put any data in any segment of the cache. They can use your cache storage. So, when you clean, it will not effect anything, whereas if you flush cache it will also flush third party module's cache. Then that module will regenerate cache in cache storage
– Shoaib Munir
Feb 27 at 7:01
yes clean ! third-pary modules .
– HaFiz Umer
Feb 27 at 7:03
yes clean ! third-pary modules .
– HaFiz Umer
Feb 27 at 7:03
when setup:di:compile run then why need to run also cache:flush and also upgrade,deploy
– HaFiz Umer
Feb 27 at 7:11
when setup:di:compile run then why need to run also cache:flush and also upgrade,deploy
– HaFiz Umer
Feb 27 at 7:11
@HaFizUmer see answer that Muhammad Ahmed has given, he described when to run other commands
– Shoaib Munir
Feb 27 at 16:53
@HaFizUmer see answer that Muhammad Ahmed has given, he described when to run other commands
– Shoaib Munir
Feb 27 at 16:53
add a comment |
di:compile
=>This command is used when you make change in di file or create new plugin or preference.
setup:upgrade
=>This command is used when you make a new module and you want to used it in your magento project.
indexer:indexer
=>When you make a change on frontend then you need to use this command.
add a comment |
di:compile
=>This command is used when you make change in di file or create new plugin or preference.
setup:upgrade
=>This command is used when you make a new module and you want to used it in your magento project.
indexer:indexer
=>When you make a change on frontend then you need to use this command.
add a comment |
di:compile
=>This command is used when you make change in di file or create new plugin or preference.
setup:upgrade
=>This command is used when you make a new module and you want to used it in your magento project.
indexer:indexer
=>When you make a change on frontend then you need to use this command.
di:compile
=>This command is used when you make change in di file or create new plugin or preference.
setup:upgrade
=>This command is used when you make a new module and you want to used it in your magento project.
indexer:indexer
=>When you make a change on frontend then you need to use this command.
answered Feb 27 at 7:21
Muhammad AhmedMuhammad Ahmed
586
586
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f263524%2fmagento2-which-command-run-and-when-to-run%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
You can find the awnser in this thread: magento.stackexchange.com/questions/138155/…
– Stijn CompactCode
Feb 26 at 17:10