[Dashboard] feat: use shared logger and cache headers - #3495
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 5 Skipped Deployments
|
dnechay
force-pushed
the
dnechay/fs-06082025
branch
from
August 6, 2025 12:58
33b73cf to
522908a
Compare
dnechay
force-pushed
the
dnechay/fs-06082025
branch
from
August 6, 2025 15:00
522908a to
0fefe24
Compare
Dzeranov
approved these changes
Aug 7, 2025
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.
Issue tracking
Follow up to #3387
Context behind the change
Added shared logger. Had to refactor files downloading logic in order to properly log errors coming from it.
Also added cache headers to responses where applicable in order to avoid unnecessary requests.
How has this been tested?
Release plan
NODE_ENV=productionvariable for corresponding service on Render (already done for stg)Potential risks; What to monitor; Rollback plan
Check that logs are displayed correctly in DD.