Closed edalzell closed 4 months ago
I'm facing issues after v5 with the static cache too, in my case the static folder is not being created. Can you check if yours is there after deployment?
Also, I didn't have the stache refresh command as a part of my deployment script, but I will add it and will let you know.
This issue is due to Prompts. Every frame change of the spinner next to the Clearing the stache...
message is being rendered as a new line.
I'm facing issues after v5 with the static cache too, in my case the static folder is not being created. Can you check if yours is there after deployment?
Also, I didn't have the stache refresh command as a part of my deployment script, but I will add it and will let you know.
That is unrelated, I'm only warming the stache, this is nothing to do with the static cache, sorry.
Clearing the stache
I guess we could not spin
?
I added an issue on Prompts.
See the response here: https://github.com/laravel/prompts/issues/151#issuecomment-2145232870
I'd recommend adding the --no-progress or --no-ansi options.
Bug description
We call
please stache:refresh
during deployment, and since we upgraded to v5 we see hundreds of these messages on every deploy:(same with
Warming the State
)How to reproduce
Use Forge to deploy a v5 and have
please stache:refresh
as part of the deploy.Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response