I saw some video about combining #cloudflareworkers with #wordpress. It required generating a static site from your WP site. This is where it kind of lost me, but I would love to see a solution that runs the static site build and deploy scripts after any change in WordPress
-
-
-
So like a WP hook that runs the plugin and calls a script that runs wrangler after update? This is a good idea...
- Još 10 drugih odgovora
Novi razgovor -
-
-
For a non-technical person, like myself, but that knows how to setup a Wordpress site, what are the advantages? Thank you in advance.
#wordpressworkers -
great question! the main advantages are around performance and security: your users are seeing a "static" version of your site, so it's immune to the usual wordpress security problems, and it's also highly cacheable - no more WP caching plugins!
- Još 5 drugih odgovora
Novi razgovor -
-
-
Forgot the
#wordpressworkers in my last message, so this time it's up front. Also curious how#cloudflareworkers would work with a#WooCommerce powered#wordpress site? If it requires a static build, how do you account for the dynamic stuff like inventory? -
things like inventory are super interesting, obviously you don't want an out-of-date version of your static site to let people buy something you don't have! this is a very jamstack-y problem because you want to have a site that is _mostly_ static w/ a few dynamic sections
- Još 2 druga odgovora
Novi razgovor -
-
-
Q2: I know how isolated workers are but Cloudflare still have access to our scripts (debuging, etc), someone interested in Workers asked me if someone from Cloudflare accessed their scripts, if they will get notified. They're worried about storing sensitive credentials in scripts
-
it is def the case that Cloudflare support will occasionally access scripts to help end users debug or investigate an issue- we have extremely strict (good!) restrictions in place about who in the org can do that- we don't notify customers (yet!) though that is a good suggestion
- Još 1 odgovor
Novi razgovor -
-
-
I’ll give it a try... my worker that protects WP, Joomla and Drupal, just takes advantage of global vars, Cache API, and only uses KV for config. This keeps the bill low. Do believe this is sensible approach or am I doing something wrong?
-
i'm not sure you are doing something wrong- i'd have to know more about your usecase! if your CMSes are mostly managing static content- Workers could be a great deploy target that would lessen your runtime complexity tho and improve the performance of your site!
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

