Running the WF plugin on a non-writable filesystem (GCP)
-
Hi there,
I’m doing a bit of exploring work on running my WP installs on GCP’s App Engine to reduce costs and improve scale-ability and I noticed a few caveats in place. Because of the way App Engine spins up ephemeral instances to satisfy increasing demand, it cannot permit your app (i.e. WordPress) to write to the local filesystem, because those instances disappear as fast as they are called into action. So you run a local copy of your site where you can execute file-writing operations (like install the plugins and themes), and redeploy to the cloud afterwards.
Okay, so far so good on a blank WP install. Now comes the questions:
As a result, I’m worried about a few plugins I like to run, amongst which most importantly: WordFence. Although I am not under the impression the scanning part actually writes files, and settings are stored in the DB, I am keenly aware that both WAF and the Falcon Engine require modifying the .htaccess file. So I’m wondering, any ideas on how to run WordFence when you can’t write any files?
- The topic ‘Running the WF plugin on a non-writable filesystem (GCP)’ is closed to new replies.