You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Environment
Configuration
Environment Variables (build-time)
astro.config.mjs
Steps to Reproduce
Push this configuration to a GitHub repo and trigger a Dokploy deploy.
Observe in the logs that pnpm install adds all 600+ packages and Astro re-optimizes 600+ images.
Trigger a second deploy without code changes.
Note that there are no “Restoring cache for…” log lines and both install & image optimization still run from scratch.
Expected Behavior
First build: Writes into /app/node_modules and /app/astro-cache.
Subsequent builds:
Actual Behavior
No cache restore steps appear.
Every build—first and subsequent—fully re-installs dependencies and re-optimizes all images.
Question
Is this a misconfiguration on my end or a bug in Nixpacks’ handling of custom cache directories?
Beta Was this translation helpful? Give feedback.
All reactions