Skip to content

Cache rendered OG images between deploys #43

Description

@TitusKirch

Before you start

  • I searched existing issues and didn't find a duplicate

What problem are you trying to solve?

Deploy #4 rendered 1,053 OG-image routes. The production workflow does not persist the available OG-image build cache. Repeatedly rendering unchanged images contributes to a prerender phase that took 158 seconds in that run.

Proposed solution

Reuse unchanged rendered OG images across production builds without serving stale images. Compare cold and warm builds of the same commit, report cache effectiveness and elapsed time, and verify invalidation after content, template, font, renderer-setting and dependency changes. Separate build and upload timings so the benefit can be measured. Preserve complete OG-image output and zero image timeouts.

Alternatives considered

Continue rendering every image. Dependency-cache tuning is lower priority: dependency installation took only 5–9 seconds in the measured runs.

Additional context

Deploy #4. Installed nuxt-og-image 6.7.8 already provides a build cache. Upstream cache implementation. Related but distinct: #36 concerns remote-source downloads, not rendered images. No time saving has been measured yet.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions