Add OG image support#38
Merged
Merged
Conversation
Following the basic principle of the NimblePublisher setup and just builds it in memory. I've done a slight optimization by having it work differently in dev and in prod: 1. In prod it builds all images at build time and then never again, serves from memory. 2. In dev it skips building at built time and instead generates them ad hoc on request, to avoid rebuilding everything on every change, while still being able to handle new pages
Dokploy Preview Deployment
|
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
1 participant
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.
Following the basic principle of the NimblePublisher setup and just builds it in memory. I've done a slight optimization by having it work differently in dev and in prod: