-
Notifications
You must be signed in to change notification settings - Fork 327
feat(databases): dedicated-database ecosystem guides + integration entries #3042
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
abnegate
wants to merge
6
commits into
feat-dedicated-db
Choose a base branch
from
dedicated-db-ecosystem
base: feat-dedicated-db
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0b5f4b2
feat(databases): add dedicated-database connect-your-stack, deploy & …
abnegate 1bcd926
feat(integrations): add dedicated-database catalog entries
abnegate 65151ad
feat(integrations): add dedicated-database integration logos and covers
abnegate 0de1cd8
chore(integrations): optimize dedicated-database logos to avif
abnegate 674c099
docs(databases): fix verify-full guidance, no Appwrite CA to download
abnegate a31af90
docs(databases): replace PostgreSQL-only notes with per-engine tabs
abnegate File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.webpbut actual files are.avifAll existing cache entries use the source file's real extension (
.png). The five new avatar entries and two cover entries added here use.webp, while the actual binary files committed in this PR are.avif(e.g.,static/images/integrations/avatars/cloudflare.avif). The image-optimization pipeline will look up each source path and won't find a match, so the cached results are effectively unreachable and the pipeline will reprocess the files on every build — or silently skip them, depending on how cache misses are handled.Three cover entries are also absent (
nextjs/cover,prisma/cover,vercel/cover) while their.aviffiles are present in the diff, so those covers have no cache entry at all. The cache should use.avifkeys for all ten new images.