Nginx
Nginx configuration experience at Legrande Legal includes a reverse proxy with cache handling and explicit bypass rules for WordPress administration, logged-in requests and other dynamic paths.
Where the engineering matters
The boundary between cacheable pages and authenticated or changing content matters more than the presence of a cache directive. The reviewed configuration defines upstream routing, forwarded request information, TLS handling, and cache exclusions.
Work represented in the portfolio
- Reverse-proxy configuration for the application upstream
- Cache and bypass rules around WordPress requests
- TLS and request-forwarding configuration
- Server operations alongside runtime and caching work
The Legrande case connects this server work with its PHP runtime upgrade and Redis object caching. Routing, application behavior, and the release process are handled as parts of the same operating environment.
Nginx configuration experience: planning a similar project
For an existing website, list the requests that must remain private or fresh before changing cache behavior. Administration, authenticated sessions and changing application responses need different treatment from public pages. The retained Legrande configuration supplies the evidence here. Its rules describe that deployment; they should be reviewed against the application and hosting environment before being reused elsewhere.
For a new project or changes to an existing system, explore ongoing website and software development.