Skip to content

Add Varnish caching proxy deployment guide#801

Merged
martin-helmich merged 11 commits intomasterfrom
feat/varnish
Jan 6, 2026
Merged

Add Varnish caching proxy deployment guide#801
martin-helmich merged 11 commits intomasterfrom
feat/varnish

Conversation

@martin-helmich
Copy link
Copy Markdown
Member

@martin-helmich martin-helmich commented Nov 4, 2025

Summary

This PR adds a comprehensive guide for deploying Varnish Cache as a caching reverse proxy in front of TYPO3 and Shopware applications on the mittwald platform.

Changes

  • New documentation: docs/platform/workloads/varnish.mdx
  • Deployment methods: Terraform, CLI, and mStudio UI instructions
  • TYPO3 integration: Configuration examples with proper user_inputs and trustedHostsPattern setup
  • VCL configuration: Examples based on the mittwald TYPO3 Varnish extension with platform-specific Host header rewriting
  • Monitoring & debugging: Guide for checking cache performance, viewing logs, and troubleshooting common issues

Key Features

  • Architecture overview explaining the Host header rewriting requirement
  • Complete Terraform example with proper TYPO3 app configuration
  • VCL examples referencing the upstream mittwald/typo3-varnishcache repository
  • Documentation on TYPO3's and Shopware's reverseProxy configuration
  • Performance considerations and cache hit ratio monitoring

Related

🤖 Generated with Claude Code

martin-helmich and others added 11 commits November 4, 2025 16:46
Add comprehensive guide for deploying Varnish Cache as a reverse proxy
in front of TYPO3 applications on the mittwald platform. Includes:

- Terraform, CLI, and mStudio UI deployment instructions
- VCL configuration with Host header rewriting for mittwald platform
- TYPO3-specific integration with mittwald/typo3-varnishcache extension
- Configuration of trustedHostsPattern for dual-hostname setup
- Monitoring, debugging, and performance optimization guidance

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Expand the Varnish caching proxy guide to support TYPO3, Shopware 5,
and Shopware 6 deployments on the mittwald platform.

Changes:
- Generalize introduction and deployment sections to be app-agnostic
- Add dedicated configuration sections for each platform:
  - TYPO3: Reference mittwald/typo3-varnishcache extension
  - Shopware 5: Cookie normalization, PURGE/BAN methods
  - Shopware 6: XKey module requirement, surrogate key invalidation
- Update VCL examples to reference official documentation
- Add Shopware 6-specific requirements (Varnish 6.0+, XKey module)
- Reorganize structure: deployment first, then app-specific configs
- Update Further Reading with Shopware documentation links

Each platform section focuses on mittwald-specific Host header
rewriting while referencing official VCL configurations.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Add complete German translation for the Varnish caching proxy documentation, including deployment instructions for Terraform, CLI, and mStudio UI, as well as application-specific configurations for TYPO3, Shopware 5, and Shopware 6.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Improve clarity and consistency across English and German versions:
- Simplify TYPO3 integration description
- Add Shopware 5 trusted proxies configuration with cloud-internal IP address details
- Streamline Shopware 6 cache invalidation documentation
- Add VCL code example for x-cache header monitoring
- Update German translation to use informal "du" form throughout

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@gandie gandie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I now understand what's going on here, though this document must be read in context with rest of documentation and probably trained to become clear. A cool move would be to provide some kind of (slow) base app, which is then accelerated via Varnish. Such addition might create a nice WOW!-moment during development/rollout, maybe even provide a simple load test, allowing people to measure before/after response times.

Nevertheless, no errors or anything else faulty found: LGTM! 🚀

@martin-helmich martin-helmich merged commit 570f41e into master Jan 6, 2026
7 checks passed
@martin-helmich martin-helmich deleted the feat/varnish branch January 6, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants