RunCloud setup for FlyingPress

RunCloud is fully compatible and works out of the box.

However, you can teak some configuration to better performance based on your stack in RunCloud.

Case 1: Nginx + Apache2 Hybrid Stack

FlyingPress automatically configures Apache2 server (using .htaccess) to serve cached pages directly. No other configuration is needed.

Case 2: Native Nginx Stack

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.

RunCloud Hub + FlyingPress

If you want to use RunCloud's internal caching system, RunCloud Hub, 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 RunCloud Hub.

FlyingPress alone

If you want FlyingPress to manage everything (without using RunCloud Hub), you can add our Nginx config to serve cached pages directly from Nginx, without using PHP.

Add custom Nginx config with RunCloud as following:

Predefined Config: I want to write my own config

Type: location.main-before

Config Name: flying-press

Config Content:

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.