I was using this for deploy the content but it is taking too much time.

php bin/magento setup:static-content:deploy 

then i figure out adding the language make fast but it still deploy all the themes.

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

how can i deploy only my theme content only?

  • FYI there is a PR that will add this capability and a lot more. I think it'll probably come out with v2.2. – thdoan Jun 28 '16 at 11:06
  • Another potential solution but for production mode magento.stackexchange.com/questions/126270/… – user42315 Jul 19 '16 at 9:29
up vote 23 down vote accepted

I'm afraid that you just can't deploy only one theme by magento console setup:static-content:deploy command.

I've been dealing with M2 frontend development for the last 2 weeks and I can affirm that the dev process it's a real PAIN! You'll lost a lot of time deploying changes due to complexity of less files hierarchy and themes fallbacks.

Anyway I'm Grunt by now here you'll find how to install, configure and use it, with Grunt you can deploy and/or recompile less files for a single theme.

So that approach it's ok if you are in "developer" mode because Grunt doesn't deploy images, fonts and javascript files to pub/static/... so magento will do it the first time required.

To activate developer mode, run:

php bin/magento  deploy:mode:set developer

If you are looking for a way to deploy the entire content for a single theme in production I sorry to say that isn't possible.

BTW I'm pretty sure that it would be a nice Feature Request to make.

EDIT: Breaking News!

I found a way to deploy all changes a little faster:

  • Install Grunt + config your theme (one for each language)
  • after each change run:
    • grunt exec:{theme_name} // Clean folders and deploy less files
    • grunt less:{theme_name} // Process less files

Voila now you'll have all your changes deployed in Just(¿?) 12~16 sec, 12 sec is my personal record!

EDIT: Breaking News 2!

Confirmed! if you are making changes to a (already deployed) .less files just run grunt less:{theme_name}.

So, you have to run grunt exec:{theme_name}only when:

  • Add/Remove/Rename a *.less File
  • Add/Remove/Rename a *.js Fils
  • Add/Remove/Rename a *.css File
  • Add/Remove/Rename a image File
  • Add/Remove requirejs-config.js

Additionally I disabled blocks, layouts and full page Caches, so any change to templates and/or xml layouts will be displayed automatically.

  • can you guid me how to make change in css through less i am stuck in topmenu. some item found but some are not but there css is there.. like .nav-sections child level0. – Qaisar Satti Feb 10 '16 at 7:35
  • It's a very large topic I recommend you to read (the entire) official guide (devdocs.magento.com/guides/v2.0/frontend-dev-guide/…). you must understand all lib > module > theme > fallback. As a starting point take a look at lib/web/css – MauroNigrele Feb 10 '16 at 7:53
  • You can see the UI Library documentation in your own store or here: magento2-demo.nexcess.net/pub/static/frontend/Magento/luma/… as well – MauroNigrele Feb 10 '16 at 7:54
  • 2
    What about when you edit a JS plugin? I found out that the changes were not getting reflected on the site. I had to remove the edited JS file from pub/static and redeploy (setup:static-content:deploy) for the changes to show. – thdoan Jun 28 '16 at 1:32
  • Not sure why this is the accepted answer, the one below is much better. – Tisch Jul 5 at 14:10

As of 2.1.1 you can now deploy specific themes or exclude themes:

Deploy specific themes:

php bin/magento setup:static-content:deploy --theme Magento/backend --theme Vendor/mytheme

Exclude themes:

php bin/magento setup:static-content:deploy --exclude-theme Magento/luma

enter image description here

Update these options are now in the documentation.

  • it didn't work for me also it didn't mention in devdocs.magento.com/guides/v2.1/config-guide/cli/… There we just 2 options. – Adeel Ishfaq Sep 17 '16 at 11:19
  • @AdeelIshfaq Like so many other things, it is not yet documented, but it does work in 2.1.1. I attached a screenshot. – Mathew Tinsley Sep 17 '16 at 21:38
  • Submitted a pull request to have the new options added to the documentation: github.com/magento/devdocs/pull/827 – Mathew Tinsley Sep 20 '16 at 1:57
  • @MathewTinsley, is it possible to deploy a specific frontend theme in all languages, and a specific backend theme only in one language? I don't need my backend in all languages.. – bpoiss Aug 9 at 12:01

In Magento 2 you are able to content deploy specific themes and also exclude themes by this commands:

Content Deploy specific themes By this command:

php bin/magento setup:static-content:deploy --theme Vendor/firsttheme --theme Vendor/secondtheme

Exclude themes By this command:

php bin/magento setup:static-content:deploy --exclude-theme Vendor/yourtheme

If you need deploys static content for particular language (en_US), and exclude other theme, and need not minify HTML files then use this command:

magento setup:static-content:deploy en_US --exclude-theme Vendor/yourtheme --no-html-minify

it seems that by now you have to deploy any language except en_US manually. i am working with 2.0.2 and develop-branch.

  • You sir, are correct. – dchayka Sep 6 '17 at 23:58

Here is shortcut to deploy only your theme

-a for area

-t for theme

-l for language

php bin/magento setup:static-content:deploy en_US -a frontend -t Magento/luma

Source

  • Shouldnt there be a -l before the en_US ? – James Harrington May 23 at 12:56

To deploy an specific theme with an specific language:

php bin/magento setup:static-content:deploy --theme Magento/backend --theme Vendor/mytheme pt_BR

If your magento is in developer mode then deploy specific theme using below commands :

Remove static content

rm -rf pub/static/*                            /*to remove files excluding .htaccess*/

rm -rf var/view_preprocessed/*                 /*to remove files excluding .htaccess*/

And then

php bin/magento setup:static-content:deploy -f --theme Vendor/theme

Your Answer

 
discard

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.