n8n persistent frontend cache grows across updates and inflates backups
-
On Cloudron 10.0.4 with the current n8n package 4.42.3 (n8n 2.38.7), I found that:
/app/data/user/.cache/n8n/public/assetshad grown to 4.5 GB and 82,398 files, while the PostgreSQL database was only 15 MB.After stopping n8n, deleting the generated public cache and restarting:
- app data: 4.5 GB ā 76 MB
- cache files: 82,398 ā 1,565
- n8n started normally and /healthz returned HTTP 200
It appears that n8nās
generateStaticAssets()copies newly hashed frontend assets into its persistent cache on every update without removing assets from previous versions. Since the Cloudron package persists the user home under/app/data/user, these stale files are also included in every backup.Could the package clean
/app/data/user/.cache/n8n/publicbefore starting n8n, or is there another intended solution?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better š
Register Login