Version Control and Configuration Management

In a typical Drupal development situation, a developer will work locally and push code and files to a remote server. In this setup, version control is crucial. What happens if a mistake is made and we need to roll back the code? What if multiple people are working on the same code? Implementing version control with a tool such as Git is a critical step in solving these common development workflow challenges.

Site Development with Features

A feature is a collection of Drupal configurations that are intentionally grouped together to satisfy a particular use case. These configurations can be used for content type declarations, views, module settings, and roles and permissions, among other things.

Cache contexts

Cache contexts are analogous to HTTP's Vary header.

Why?

Cache contexts provide a declarative way to create context-dependent variations of something that needs to be cached. By making it declarative, code that creates caches becomes easier to read, and the same logic doesn't need to be repeated in every place where the same context variations are necessary.

Examples:

Server configuration with Apache in Gnu/Linux

For your testing server, you can have the same IP. First you have to enable this two modules
proxy_module /usr/lib/apache2/modules/mod_proxy.so
proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so

Then in the /etc/sites-available file for your site, you have to make two entrances:

(change drupal7 with your site name and the ports, as you configure in the nodejs.config.js)

Cacheability of render arrays

Short version in the API documentation: Render API overview: Caching

Render arrays determine what is shown to the user. Therefore, arrays also determine how cacheable a response is.

The Drupal 8 render pipeline

or: how Drupal renders pages

First, you need to know the general routing concepts: please read Route controllers for simple routes first.

Pages

Subscribe with RSS Subscribe to RSS - No known problems