Skip to content
New issue

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

command line option to clear static assets #1811

Closed
markshust opened this issue Sep 7, 2015 · 6 comments
Closed

command line option to clear static assets #1811

markshust opened this issue Sep 7, 2015 · 6 comments

Comments

@markshust
Copy link
Contributor

There is a flag on the ./bin/magento module:enable command: --clear-static-content

Unfortunately, this only appears to be on the module-enable option. If static assets are desired to be cleared at any other time, this isn't an option.

I believe there should be a new command under ./bin/magento that just clears this static content, something like:
./bin/magento cache:clear-static-content

I'm not sure if static assets are considered a cached asset, so this may need some revision.

Thanks!
Mark

@ghost
Copy link

ghost commented Sep 7, 2015

Fair point. There is one other time that static view files are cleared: switching from developer <> production modes.

http://devdocs.magento.com/guides/v2.0/config-guide/cli/config-cli-subcommands-mode.html

@gotbahn
Copy link

gotbahn commented Sep 8, 2015

@markoshust there is grunt clean, maybe would be helpful

@alankent
Copy link

alankent commented Sep 8, 2015

We need this separation potentially for automated deployment pipelines. Grunt might be a short term workaround, but must not be mandatory for that (e.g. switching from dev to prod mode). We should have a separate magento command if its needed. We have been introducing these CLI commands to avoid "oh, for use case X remove directory Y" - we want it to be "for use case X run command Y" so if we change things internally related to "use case X", we can adjust "command Y" to follow the new rules without breaking existing deployment pipelines.

@tdgroot
Copy link
Member

tdgroot commented May 2, 2016

Really missing this feature as well, people shouldn't be removing directories when deploying..
Thinking about creating my own pull request to get it on the rails asap.

@mbrinton01
Copy link

Created internal issue MAGETWO-57193 to track this suggestion

@piotrekkaminski
Copy link
Contributor

Thank you for your submission.

We recently made some changes to the way we process GitHub submissions to more quickly identify and respond to core code issues.

Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here).

We are closing this GitHub ticket and have moved your request to the new forum.

okorshenko pushed a commit that referenced this issue Dec 11, 2017
[performance] MAGETWO-83326: Run scenarios on PAT for 2.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants