Show HN: Building a zero-latency WordPress front-end

The following section configures reverse-proxying for the WordPress admin page:

The following section controls Nginx’s interaction with Node:

We select the cache zone we defined earlier with the directive. The directive is there to keep Nginx from creating separate cache entries when requests to the same URL have different headers (additional compression methods, for example). They let us figure out whether a request has resulted in a cache hit when we examine it using the browser’s development tools:

The following Express handler (index.js) is invoked when Nginx asks for an HTML page.

Source: github.com