Skip to content

feat(backend): add CDN edge caching with surrogate keys#677

Merged
Smartdevs17 merged 5 commits into
Smartdevs17:mainfrom
od-hunter:feature/cdn-edge-cache-surrogate-keys
Jun 25, 2026
Merged

feat(backend): add CDN edge caching with surrogate keys#677
Smartdevs17 merged 5 commits into
Smartdevs17:mainfrom
od-hunter:feature/cdn-edge-cache-surrogate-keys

Conversation

@od-hunter

Copy link
Copy Markdown
Contributor

Closes #595

Add cache header middleware, Fastly/Cloudflare purge client, public API
routes for plans/pricing/features/config, VCL snippets, and deploy workflow.
@drips-wave

drips-wave Bot commented Jun 25, 2026

Copy link
Copy Markdown

@od-hunter Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Combine upstream Redis cache module with CDN purge client, surrogate key
middleware, and public API routes. Resolve package-lock.json to retain
both express and graphql dependencies.
@gitguardian

gitguardian Bot commented Jun 25, 2026

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
34266369 Triggered Generic Password 7d57c93 backend/config/tests/redis.test.ts View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@Smartdevs17 Smartdevs17 merged commit ed8d7cf into Smartdevs17:main Jun 25, 2026
1 check failed
abimbolaalabi pushed a commit to abimbolaalabi/SubTrackr that referenced this pull request Jun 26, 2026
)

* feat(backend): add CDN edge caching with surrogate keys

Add cache header middleware, Fastly/Cloudflare purge client, public API
routes for plans/pricing/features/config, VCL snippets, and deploy workflow.

* chore: automated code formatting fixes via CI pipeline

* chore: automated code formatting fixes via CI pipeline
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.

Add CDN edge caching for API responses with surrogate keys

2 participants