Docs / Hosting / GridPane


FlyingPress is fully compatible with GridPane.

In Nginx, FlyingPress will use PHP to serve cached pages. You can choose any of the following methods to serve cached pages directly from Nginx.

1. Nginx FastCGI/Redis Caching + FlyingPress

If you want to use GridPane's internal caching FastCGI or Redis page caching, simply turn off caching inside FlyingPress settings.

In this way, FlyingPress will optimize all pages, but will not cache pages. The cache will be handled by Nginx FastCGI/Redis.

2. FlyingPress alone

If you want FlyingPress to manage everything (without using GridPane's internal caching), you can add our Nginx config to serve cached pages directly from Nginx, without using PHP.

First disable Nginx FastCGI/Redis page caching. Then add the following Nginx config to sites/ with the file name flying-press-main-context.conf:

location ~* \.html$ {
  charset UTF-8;
  add_header x-flying-press-cache HIT;
  add_header x-flying-press-source Nginx;
  add_header cache-control "no-cache, must-revalidate, max-age=0";

set $flying_press_cache 1;
set $flying_press_url "/wp-content/cache/flying-press/$http_host/$request_uri/index.html";
set $flying_press_file "$document_root/wp-content/cache/flying-press/$http_host/$request_uri/index.html";

if ($request_method = POST) {
  set $flying_press_cache 0;

if ($is_args) {
  set $flying_press_cache 0;

if ($http_cookie ~* "(wp\-postpass|wordpress_logged_in|comment_author|woocommerce_cart_hash|edd_items_in_cart)") {
  set $flying_press_cache 0;

if (!-f "$flying_press_file") {
  set $flying_press_cache 0;

if ($flying_press_cache = 1) {
  rewrite .* "$flying_press_url" last;

Verify Nginx config with nginx -t and finally, restart using gp ngx reload

To verify if it's working, check the response header of your site from an Incognito window. You'll see x-flying-press-source: Nginx indicating that it’s served via Nginx.