@mealto When this plugin will create a reverse-proxy zone, it will intentionally not enable Perma Cache because it’s not supported in our use case.
You can use “Perma Cache” only for static files via official plugin together.
1. Create a new zone static-example-com
2. Enable Perma Cache for it
3. Install & Activate bunny.net plugin for the static files.
Thanks
Thread Starter
mealto
(@mealto)
Hey cool. So you are saying we can run your cool plugin + the official Bunny plugin to enable Perma-cache and try and increase % HIT?
Exactly. Both plugin can be used together.
This one will be for HTML.
Official one will be for static files exclusively with a seperate pull zone.
This way you can have consistent best performance for the static files.
Thanks
Thread Starter
mealto
(@mealto)
Let me keep testing. Any other tips and tricks I should know while using your plugin and this method?
Looking at site URL I can offer personalized suggestions 🙂
Rest everything is written inside ‘Help’ menu.
Thread Starter
mealto
(@mealto)
Thank you Gulshan. You are one smart guy to be able to figure out how to set up your plugin to configure Bunny as a reverse proxy. Well done.
Thank you so much for your kind words. It encourages to build cool things.
Thread Starter
mealto
(@mealto)
One last question. Bunny Support is saying we may not need Perma-Cache. If that is the case, is there an advantage to run the official Bunny plugin to enable caching of other assets (js, css, images) and let your plugin edge cache HTML as a reverse proxy? I think that’s how it works correct?
Bunny Support is saying we may not need Perma-Cache.
Please note: Team bunny.net is not responsible for offering support for this plugin.
As I said already, you can run side-by-side both plugins at a time. I have tested and it works.
Thread Starter
mealto
(@mealto)
Understood. Your instructions above was to create a new zone. Can we still use the original zone that your plugin created for the Bunny plugin? ie. both plugins using the same pull zone?
For using perma cache for the static files, you need create a seperate Pull Zone.
Here’s the instructions https://www.gulshankumar.net/bunnycdn/#how-to-use
You should not use same pull zone as both are going to be for two different purpose.
Can we still use the original zone that your plugin created for the Bunny plugin? ie. both plugins using the same pull zone?
You shouldn’t use same zone. Just create manually. There is no shortcut.
https://www.gulshankumar.net/bunnycdn/#how-to-use
Thread Starter
mealto
(@mealto)
Thanks for the tutorial. So I am trying to add a custom hostname for the 2nd pull zone. Your instructions say to create a CNAME for the host @ to install the SSL but the DNS already has a CNAME attached to the host @ already from following the instructions inside your plugin. Any ideas?
Your instructions say to create a CNAME for the host @
Please send me a screenshot link where such text is written.
For static files, you can use default hostname as well. But if you create custom like cdn subdomain then you would be pointing like
CNAME - cdn - static-example-com.b-cdn.net - TTL: Automatic - DNS only mode, not proxy
Thread Starter
mealto
(@mealto)
ok, after a few days of testing and getting help with Bunny support, we have determined Perma-Cache is not needed for this particular site. So… do we even need to set up the official Bunny plugin if we are running this one? Not sure if this plugin also has a function to accomplish the same thing as the official plugin. Any advice would be greatly appreciated..
