Magento2 – Custom VCL Snippet for Fastly Not Deployed

adobe-commercefastlymagento2magento2-cloudvarnish

We are using Adobe Commerce Cloud v2.4.4 – with the fastly extension 1.2.185

In the documention for custom VCL snippets there is a section for automated custom VCL snippets deployment.

We did add our custom snippet deliver_100_setHttpResponseHeaderXContentTypeOptionsNosniff.vcl to our git repository – below the path var/vcl_snippets_custom.

After performing a deployment to our cloud-environment we expected to find the custom snippet on the server below ~/var/vcl_snippets_custom.
But the file wasn't there.

Why?

Best Answer

I got an answer on Github from one of the contributors of this extension: the automated deployment of VCL snippets is currently not supported by the Adobe Cloud deployment process.

Related Solutions

Magento – the proper way of positioning/ordering CSS files in Magento 2

Magento2 has no built-in mechanism for this so I decided to treat it as an opportunity to write my first Magento2 extension. The Quickshiftin\Assetorderer extension is now available on GitHub!

Once you have the extension installed you can specify an order attribute in your css XML tags.

<head>
  <css src="css/page/home.css" order="100"/>
</head>

You can also use the order attribute in layout XML files such as default_head_blocks.xml. Any css tags you don't specify an order for are treated as if they have an order of 1.

Magento2 Deployment Workflow – Changes Not Deployed

So i got it working. I will post here a general guide for the developer mode and what needs to be done. With the shown shell commands i assume that you are in your Magento2 root directory.

To get the developer workflow up and running, there are a few things to do. First, activate developer mode in magerun: bin/magento deploy:mode:set developer. To be sure developer mode is active, check your app/etc/env.php if the developer mode is set: 'MAGE_MODE' => 'developer'. After this, also add / uncomment this line in .htaccess and pub/.htaccess SetEnv MAGE_MODE developer. After this, remove all your static and generated content: rm -rf var/page_cache/* var/view_preprocessed/* var/generation/* var/cache/* pub/static/*

IMPORTANT: Check that no uncommented content is after this command! SetEnv MAGE_MODE developer #Comment will not work. This caused the problem in my case, because in the default htaccess a comment exists.

Original pub/.htaccess line: # SetEnv MAGE_MODE default # or production or developer

Best Answer

Related Solutions

Magento – the proper way of positioning/ordering CSS files in Magento 2

Magento2 Deployment Workflow – Changes Not Deployed

Related Topic