Download the PHP package bagisto/bagisto-varnish without Composer
On this page you can find all versions of the php package bagisto/bagisto-varnish. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package bagisto-varnish
Varnish Integration for Bagisto
This package integrates Varnish Cache with Bagisto to boost site performance by delivering cached pages quickly, while still supporting dynamic components through ESI (Edge Side Includes) or AJAX-based dynamic views.
📌 Features
- ⚡ Full-page caching via Varnish
- 🔄 Automatic cache purging on product, category, or content updates
- 🔍 ESI support for dynamic blocks
- 🖱 AJAX-based dynamic view loading for improved Core Web Vitals
- 🛠 Artisan commands for cache management
- 🖥 Admin tools for purging cache & exporting VCL
- 🎨 Theme-ready Blade components
- 🛡 Middleware for cache headers (cacheable & non-cacheable routes)
🔄 Request Flow
Explanation:
- 443 (HTTPS) → Nginx handles SSL termination and forwards traffic.
- 80 (HTTP) → Varnish Proxy caches and serves pages, or passes the request to the backend.
- 8080 → Bagisto (Laravel app) generates fresh content when needed.
Flow Summary: Browser → Nginx → Varnish Proxy → Bagisto → Response (cached or fresh)
📦 Installation
1. Install via Composer
2. Register the Service Provider
In bootstrap/providers.php:
Note: Autoloading via Composer’s package auto-discovery is not possible for this provider. The registry order matters—
VarnishServiceProvidermust be listed after the Shop package or at the end of the providers array. Auto-discovery would load it too early, which can cause issues.
3. Publish Assets & Config
⚙️ Varnish Server Configuration
-
Install Varnish 6.x on your server.
-
Replace
/etc/varnish/default.vclwith the provided file: - Restart Varnish:
🎨 Theme Integration
You can integrate dynamic content in two ways:
1 – Define Dynamic Views / Fragments
In config/varnish.php, define a key (identifier) and its corresponding Blade view path:
- Key → Used in ESI or AJAX call (
customer-desktop-dropdown) - Path → Full Blade view path to render (
varnish::...)
2 – ESI Include
- Injects content at the Varnish level (server-side).
- Appears immediately on page load.
- May affect LCP/FCP if the backend is slow.
3 – AJAX Dynamic View (Recommended for LCP)
- Loads via AJAX after user interaction.
- Improves LCP/FCP.
- Ideal for non-critical dropdowns, modals, and menus.
🗂 Cache-Control Headers
For routes that should NOT be cached by Varnish:
For routes that should be cached:
(Example: 7 days)
Middleware for Cache Headers in Bagisto
We’ve created a middleware Webkul\Varnish\Http\Middleware\VarnishCache to handle cache headers.
Attach it to routes like this:
🛠 UI Configuration (Export VCL)
Navigate to: Admin → Configuration → Full Page Cache → Configuration
Select Varnish as the cache application, then provide the following:
- Access List – IPs allowed to purge the cache (e.g.,
localhost). - Varnish Host URL – Varnish server IP and port for purging/banning cache via UI.
- Backend Host URL – Laravel Bagisto server IP used in the exported VCL.
- Backend Host Port – Laravel Bagisto server port used in the exported VCL.
- Grace Period – Duration for serving stale content if the backend is slow or unavailable.
🛠 Cache Management
Navigate to: Admin → Configuration → Full Page Cache → Cache Management
- Purge by URLs – Enter full URLs (comma-separated) to clear specific cache entries. Paths and domains must match exactly.
- Purge Everything – Clears all cache entries from Varnish. Use with caution, as it may temporarily affect performance.
🛡 Automatic Cache Purging
The package automatically purges cache when:
- Products, categories, pages, orders, reviews, refunds, or theme changes occur.
You can also manually trigger purging by adding your own events in EventServiceProvider and calling:
🖥 Admin Panel Tools
- Purge Full Cache
- Purge by URL
- Export VCL
🚀 Best Practices
- Use ESI for small, critical personalized blocks (e.g., login status, cart count).
- Use AJAX dynamic views for non-critical interactive elements to improve Core Web Vitals.
- Set Cache-Control headers with appropriate TTL values to control caching behavior.
- Always test on a staging environment before deploying to production.
- Monitor LCP, FCP, and TTFB after enabling Varnish.
