Contents
- Overview of static view files deployment
- First steps
- Deploy static view files
- Troubleshooting the static view files deployment tool
Overview of static view files deployment
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.
The term static view file refers to the following:
- 鈥淪tatic鈥 means it can be cached for a site (that is, the file is not dynamically generated). Examples include images and CSS generated from LESS.
- 鈥淰iew鈥 refers to presentation layer (from MVC).
Static view files are located in the <your Magento install dir>/pub/static
directory, and some are cached in the <your Magento install dir>/var/view_preprocessed
directory as well.
Static view files deployment is affected by Magento modes as follows:
- Developer mode: Magento generates them on demand, but the rest are cached in a file for speed of access.
-
Default and production modes: Static files are not generated or cached.
You must write static view files to the Magento file system manually using the command discussed in this topic; after that, you can restrict permissions to limit your vulnerabilities and to prevent accidental or malicious overwriting of files.
Developer mode only: When you install or enable a new module, it might load new JavaScript, CSS, layouts, and so on. To avoid issues with static files, you must clean the old files to make sure you get all the changes for the new module.
You can clean generated static view files in any of the following ways:
- Manually by clearing the
pub/static
andvar/view_preprocessed
directories and subdirectories. except forpub/static/.htaccess
.
To clear thepub/static
directory of all files except.htaccess
, enter the following command:
find . -depth -name .htaccess -prune -o -delete
- Using the Magento command line. Several commands support an optional parameter
--clear-static-content
, which cleans generated static view files. For example, see Enable or disable modules. - In the Magento Admin. Go to System > Tools > Cache Management and click Flush Static Files Cache.
First steps
-
Log in to the Magento server as, or switch to, a user who has permissions to write to the Magento file system. One way to do this is to switch to the Magento file system owner.
If you use the bash shell, you can also use the following syntax to switch to the Magento file system owner and enter the command at the same time:
su <Magento file system owner> -s /bin/bash -c <command>
-
To run Magento commands from any directory, add
<your Magento install dir>/bin
to your systemPATH
.Because shells have differing syntax, consult a reference like unix.stackexchange.com.
bash shell example for CentOS:
export PATH=$PATH:/var/www/html/magento2/bin
You can also run the commands in the following ways:
cd <your Magento install dir>/bin
and run them as./magento <command name>
php <your Magento install dir>/bin/magento <command name>
<your Magento install dir>
is a subdirectory of your web server's docroot. Need help locating the docroot? Click here.
In addition to the command arguments discussed here, see Common arguments.
Deploy static view files
To deploy static view files:
- Log in to the Magento server as, or switch to, the Magento file system owner.
- Delete the contents of
<your Magento install dir>/pub/static
. -
Run the static view files deployment tool
<your Magento install dir>/bin/magento setup:static-content:deploy
.If you enable static view file merging in the Magento Admin, the
pub/static
directory system must be writable.
Command options:
magento setup:static-content:deploy <lang> ... <lang> [--dry-run]
The following table discusses the meanings of this command鈥檚 parameters and values.
Option | Description | Required? |
---|---|---|
<lang> | Space-separated list of ISO-636 language codes for which to output static view files. (Default is You can find the list by running |
No |
--dry-run | Include to view the files output by the tool without outputting anything. |
No |
For example, to deploy static view files for the pt_BR
language, enter
magento --ansi setup:static-content:deploy pt_BR
Following are some sample messages that display to indicate successful deployment:
Requested languages: pt_BR
=== frontend -> Magento/luma -> pt_BR ===
... progress indicator ...
Successful: 1613 files; errors: 0
=== frontend -> Magento/blank -> pt_BR ===
... progress indicator ...
Successful: 1620 files; errors: 0
=== adminhtml -> Magento/backend -> pt_BR ===
... progress indicator ...
Successful: 1626 files; errors: 0
=== Minify templates ===
... progress indicator ...
Successful: 858 files modified
---
New version of deployed files: 1430773903
Troubleshooting the static view files deployment tool
Install the Magento software first; otherwise, you cannot run the static view files deployment tool.
Symptom: The following error is displayed when you run the static view files deployment tool:
ERROR: You need to install the Magento application before running this utility.
Solution:
Use the following steps:
-
Install the Magento software in any of the following ways:
- Log in to the Magento server as, or switch to, the Magento file system owner.
- Delete the contents of
<your Magento install dir>/pub/static
directory.
Find us on