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
Please set STATAMIC_STACHE_WATCHER to false in the config by default. You can always set this to true in your .env file but this will make sure you don't accidentally set it to true on production. Took me a while to figure out why performance was slow.
Regards,
Mark
The text was updated successfully, but these errors were encountered:
Unfortunately we can’t do that — if we set it to false then everyone building sites for the first time will be confused by why their site doesn’t update when they’re making changes in the code.
On Jun 13, 2024, at 11:43 AM, Mark de Raaf ***@***.***> wrote:
Please set STATAMIC_STACHE_WATCHER to false in the config by default. You can always set this to true in your .env file but this will make sure you don't accidentally set it to true on production. Took me a while to figure out why performance was slow.
Regards,
Mark
—
Reply to this email directly, view it on GitHub <#1178>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAK5Q5C3GABXHSTTCS6FKLZHFSVZAVCNFSM6AAAAABJIAXVTSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM2TANRYGQYTKOA>.
You are receiving this because you are subscribed to this thread.
Please set STATAMIC_STACHE_WATCHER to false in the config by default. You can always set this to true in your .env file but this will make sure you don't accidentally set it to true on production. Took me a while to figure out why performance was slow.
Regards,
Mark
The text was updated successfully, but these errors were encountered: