When to compile and deploy content












1














After a year or so of working in Developer Mode, I'm now using Production Mode.



As I deploy updates to modules or designs, I'm wondering when I should run the below commands. At the moment, my order of operations is:




  1. Update files in app/code or app/design

  2. Run bin/magento setup:di:compile

  3. Run bin/magento setup:static-content:deploy en_GB


Is this still necessary when updating something like a stylesheet or template?






setup-di-compile magento2.2.7







share|improve this question





























    1














    After a year or so of working in Developer Mode, I'm now using Production Mode.



    As I deploy updates to modules or designs, I'm wondering when I should run the below commands. At the moment, my order of operations is:




    1. Update files in app/code or app/design

    2. Run bin/magento setup:di:compile

    3. Run bin/magento setup:static-content:deploy en_GB


    Is this still necessary when updating something like a stylesheet or template?






    setup-di-compile magento2.2.7







    share|improve this question



























      1












      1








      1







      After a year or so of working in Developer Mode, I'm now using Production Mode.



      As I deploy updates to modules or designs, I'm wondering when I should run the below commands. At the moment, my order of operations is:




      1. Update files in app/code or app/design

      2. Run bin/magento setup:di:compile

      3. Run bin/magento setup:static-content:deploy en_GB


      Is this still necessary when updating something like a stylesheet or template?






      setup-di-compile magento2.2.7







      share|improve this question















      After a year or so of working in Developer Mode, I'm now using Production Mode.



      As I deploy updates to modules or designs, I'm wondering when I should run the below commands. At the moment, my order of operations is:




      1. Update files in app/code or app/design

      2. Run bin/magento setup:di:compile

      3. Run bin/magento setup:static-content:deploy en_GB


      Is this still necessary when updating something like a stylesheet or template?






      setup-di-compile magento2.2.7




      setup-di-compile magento2.2.7






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday









      PЯINCƏ

      7,73121136




      7,73121136










      asked yesterday









      Craig

      7271419




      7271419






















          2 Answers
          2






          active

          oldest

          votes


















          2














          php bin/magento setup:upgrade :




          Upgrades the Magento application, DB data, and schema




          php bin/magento setup:di:compile :




          Generates DI configuration and all missing classes that can be
          auto-generated




          php bin/magento setup:static-content:deploy :




          Deploys static view files




          CSS where is it placed ? in view files : app/design/frontend/{Theme}/{name}/web/css/custom.css or app/code/Vendor/Name/view/frontend/web/css/custom.css So YES you need to deploy the static-contents on production mode.



          Magento DevDocs says :




          The static view files deployment command enables you to write static
          files to the Magento file system when the Magento software is set for
          production mode.




          Good luck






          share|improve this answer





























            2














            The brief answer is yes for stylesheet/templates you would then need to redeploy the static content. You wouldn't need to compile.



            Compilation would be required for something like, for example, adding a new extension or adding a new instance of a model into an existing module.






            share|improve this answer





















              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
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f256807%2fwhen-to-compile-and-deploy-content%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              2














              php bin/magento setup:upgrade :




              Upgrades the Magento application, DB data, and schema




              php bin/magento setup:di:compile :




              Generates DI configuration and all missing classes that can be
              auto-generated




              php bin/magento setup:static-content:deploy :




              Deploys static view files




              CSS where is it placed ? in view files : app/design/frontend/{Theme}/{name}/web/css/custom.css or app/code/Vendor/Name/view/frontend/web/css/custom.css So YES you need to deploy the static-contents on production mode.



              Magento DevDocs says :




              The static view files deployment command enables you to write static
              files to the Magento file system when the Magento software is set for
              production mode.




              Good luck






              share|improve this answer


























                2














                php bin/magento setup:upgrade :




                Upgrades the Magento application, DB data, and schema




                php bin/magento setup:di:compile :




                Generates DI configuration and all missing classes that can be
                auto-generated




                php bin/magento setup:static-content:deploy :




                Deploys static view files




                CSS where is it placed ? in view files : app/design/frontend/{Theme}/{name}/web/css/custom.css or app/code/Vendor/Name/view/frontend/web/css/custom.css So YES you need to deploy the static-contents on production mode.



                Magento DevDocs says :




                The static view files deployment command enables you to write static
                files to the Magento file system when the Magento software is set for
                production mode.




                Good luck






                share|improve this answer
























                  2












                  2








                  2






                  php bin/magento setup:upgrade :




                  Upgrades the Magento application, DB data, and schema




                  php bin/magento setup:di:compile :




                  Generates DI configuration and all missing classes that can be
                  auto-generated




                  php bin/magento setup:static-content:deploy :




                  Deploys static view files




                  CSS where is it placed ? in view files : app/design/frontend/{Theme}/{name}/web/css/custom.css or app/code/Vendor/Name/view/frontend/web/css/custom.css So YES you need to deploy the static-contents on production mode.



                  Magento DevDocs says :




                  The static view files deployment command enables you to write static
                  files to the Magento file system when the Magento software is set for
                  production mode.




                  Good luck






                  share|improve this answer












                  php bin/magento setup:upgrade :




                  Upgrades the Magento application, DB data, and schema




                  php bin/magento setup:di:compile :




                  Generates DI configuration and all missing classes that can be
                  auto-generated




                  php bin/magento setup:static-content:deploy :




                  Deploys static view files




                  CSS where is it placed ? in view files : app/design/frontend/{Theme}/{name}/web/css/custom.css or app/code/Vendor/Name/view/frontend/web/css/custom.css So YES you need to deploy the static-contents on production mode.



                  Magento DevDocs says :




                  The static view files deployment command enables you to write static
                  files to the Magento file system when the Magento software is set for
                  production mode.




                  Good luck







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered yesterday









                  PЯINCƏ

                  7,73121136




                  7,73121136

























                      2














                      The brief answer is yes for stylesheet/templates you would then need to redeploy the static content. You wouldn't need to compile.



                      Compilation would be required for something like, for example, adding a new extension or adding a new instance of a model into an existing module.






                      share|improve this answer


























                        2














                        The brief answer is yes for stylesheet/templates you would then need to redeploy the static content. You wouldn't need to compile.



                        Compilation would be required for something like, for example, adding a new extension or adding a new instance of a model into an existing module.






                        share|improve this answer
























                          2












                          2








                          2






                          The brief answer is yes for stylesheet/templates you would then need to redeploy the static content. You wouldn't need to compile.



                          Compilation would be required for something like, for example, adding a new extension or adding a new instance of a model into an existing module.






                          share|improve this answer












                          The brief answer is yes for stylesheet/templates you would then need to redeploy the static content. You wouldn't need to compile.



                          Compilation would be required for something like, for example, adding a new extension or adding a new instance of a model into an existing module.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered yesterday









                          performadigital

                          7301517




                          7301517






























                              draft saved

                              draft discarded




















































                              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.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • 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.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f256807%2fwhen-to-compile-and-deploy-content%23new-answer', 'question_page');
                              }
                              );

                              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







                              -

                              Popular posts from this blog

                              1300-talet

                              Image
                              Den här artikeln handlar om hundraårsperioden 1300–1399. För decenniet 1300–1309, se 1300-talet (decennium). .mw-parser-output .infobox{border:1px solid #aaa;background-color:#f9f9f9;color:black;margin:.5em 0 .5em 1em;padding:.2em;float:right;clear:right;width:22em;text-align:left;font-size:88%;line-height:1.6em}.mw-parser-output .infobox td,.mw-parser-output .infobox th{vertical-align:top;padding:0 .2em}.mw-parser-output .infobox caption{font-size:larger}.mw-parser-output .infobox.bordered{border-collapse:collapse}.mw-parser-output .infobox.bordered td,.mw-parser-output .infobox.bordered th{border:1px solid #aaa}.mw-parser-output .infobox.bordered .borderless td,.mw-parser-output .infobox.bordered .borderless th{border:0}.mw-parser-output .infobox-showbutton .mw-collapsible-text{color:inherit}.mw-parser-output .infobox.bordered .mergedtoprow td,.mw-parser-output .infobox.bordered .mergedtoprow th{border:0;border-top:1px solid #aaa;border-right:1px solid #aaa}.mw-parser-output ...
                              Read more

                              1300-talet

                              Image
                              Den här artikeln handlar om hundraårsperioden 1300–1399. För decenniet 1300–1309, se 1300-talet (decennium). .mw-parser-output .infobox{border:1px solid #aaa;background-color:#f9f9f9;color:black;margin:.5em 0 .5em 1em;padding:.2em;float:right;clear:right;width:22em;text-align:left;font-size:88%;line-height:1.6em}.mw-parser-output .infobox td,.mw-parser-output .infobox th{vertical-align:top;padding:0 .2em}.mw-parser-output .infobox caption{font-size:larger}.mw-parser-output .infobox.bordered{border-collapse:collapse}.mw-parser-output .infobox.bordered td,.mw-parser-output .infobox.bordered th{border:1px solid #aaa}.mw-parser-output .infobox.bordered .borderless td,.mw-parser-output .infobox.bordered .borderless th{border:0}.mw-parser-output .infobox-showbutton .mw-collapsible-text{color:inherit}.mw-parser-output .infobox.bordered .mergedtoprow td,.mw-parser-output .infobox.bordered .mergedtoprow th{border:0;border-top:1px solid #aaa;border-right:1px solid #aaa}.mw-parser-output ...
                              Read more

                              Display a custom attribute below product name in the front-end Magento 1.9.3.8

                              Image
                              0 I need to display a custom attribute bellow the product name and I don't know how can I call this attribute. I am editing the file /app/design/frontend/templatemela/MAG100219_1/template/catalog/product/view.phtml But how can I call this attribute in php? I tried calling a string echo with the name I put in the attribute, but it didn't work. Code is as below: <div class="page-title product-title"> <h1><?php echo $_helper->productAttribute($_product, $_product->getName(), 'name') ?></h1> </div> <div class="codigoinmetro"> <h2><?php echo $_helper->productAttribute($_product, $_product->getName(), 'registroinmetro') ?></h2> </div> php attrib...
                              Read more