>A Complete Guide on Magento 2 Deploy Static Content

A Complete Guide on Magento 2 Deploy Static Content

These days, most modern websites are always changing. Websites constantly modify their layout, content, and accessible configurations, basing on the request of the users. In many cases, depending on who accesses it, different contents are displayed to each user. This content is called dynamic content; it can change on a per-request basis.

Static content, on the contrary, changes little over time, it does not vary to the request of each access. Therefore, it’s generally time-saving with cache, process, and transfer.

This Magento 2 tutorial would give you a complete guide on Magento 2 deploy static content (or static view file). After the deployment, developers will be able to write static files to the Magento 2 system when your system is on the production mode.

Configuring Magento 2 deploy static content in developer mode

In developer mode, you have to clean the old files of CSS, JavaScript, Layouts, etc. to make sure that static files run well when you enable a new module. Here are the steps you can follow to clean generated static view files:

Step 1: Use the below command to manually clear all the files under pub/static directory except .htaccess file:

find. -depth -name .htaccess -prune -o -delete

Step 2: In your Magento 2 Admin Panel, you can do an automated clearing of generated static view files by navigating to System/ Tools/ Cache Management and clicking on the Flush Static Files Cache.

Using CLI to deploy Magento 2 static content in production mode

First off, you can find static view files in dir/pub/static and some of them in dir/var/view_preprocessed directory.

Next, those static view files need to be written to your Magento 2 file system manually by the CLI command.

Step 1: Login or Switch to your Magento 2 file system owner  

Step 2: Remove the content under <your Magento install dir>/pub/static.

Step 3: Run the static view files deployment tool by <your Magento install dir>/bin/magento setup:static-content:deploy.

Note: when you enable merging static view files in your Magento Admin, pub/static directory system must be writable.

Troubleshooting deployment tool of the static content

While deploying the static content, you might be facing the below issue.

magento 2 deploy static content troubleshooting

If you come up with the error above, just follow these steps to tackle the problem.

  1. Install Magento 2 using the command line or setup wizard Using Command Line or Setup Wizard for Magento 2 installation
  2. Login or Switch to your Magento 2 system owner
  3. Remove contents under <your Magento 2 install dir>/pub/static
  4. And run the Static Con deployment tool <your Magento install dir>/bin/Magento setup:static-content:deploy.

 

Tips for developers to customize the static content deployment tool

When you want to customize an implementation of the static content deployment tool, we recommend you use only atomic file writing for files that should be available on the client. In case you use non-atomic file writing, those files might be loaded on the client with partial content.

To make the file atomic, you should try writing to files stored in a temporary directory then copy or move them to the destination directory (from where they are loaded to clients) after writing is over.

In case you have any further question regarding this blog, Website Development or our extension store on Magento 1 and Magento 2, please feel free to contact us. Our support team is always willing to aid you with the best service of FREE installation, FREE update, FREE 1-year support and 30-day money back guarantee.