Repository navigation
Release Nginx Cache 0.3.0: measured KPIs, safe previews and dashboard updates - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The dashboard previously inferred a 100% cache hit rate from directory availability and hid the cause of failed purge previews. This release measures eligible Nginx requests over the last hour, shows the denominator and explicit missing/empty states, and previews expired cache layouts without creating or modifying cache files, sentinels or locks.
The dashboard now uses NGINX green accents, black action buttons, consistent section headings and a responsive metrics panel with collapsed measurement details. Generated Nginx includes support validated cache limits and separate HTTP/server/logging/FastCGI contexts; an exact empty-query map entry restores ordinary anonymous caching. Deferred prewarming runs in durable five-URL batches, checkpoints successful URLs, preserves the failure budget and rejects HTTP errors and redirects.
Prepare v0.3.0 with the existing tagged WordPress archive and Plugin Check workflow. Production archives include the dashboard stylesheet and exclude prototypes and development files. The new local feature-set roadmap is outside this branch and is not included in this PR.
Validation:
composer qa: coding standards, PHPStan and 71 unit tests / 313 assertions passed.composer tests:nginx: nine real HTTP cases passed, including cache-root creation, query maps, JSON metrics and preservation of existing access logs.ca0a0d76cd526a1a60c9965857e197d67dfc8152: QA run.2c2cfd1509f29c3bb9aff4487e25a7d59d2ad681. Release v0.3.0 is published with the ZIP and SHA-256 file; the unauthenticated public download matches the verified archive and all 2,435 manifest checksums. Packagist resolves to the same commit.Deployment: regenerate the relevant Nginx includes and apply them through the existing server deployment process to enable metrics logging and updated cache rules/limits. The plugin does not reload Nginx. WordPress cron must run reliably to process deferred work.