Closed petertgiles closed 2 weeks ago
Looks like this breaks Graphiql as well. I needed a quick fix to get it going again:
Any risks to just handing over ownership of the storage dir to www-data
? That is what the laravel docs recommend.
Any risks to just handing over ownership of the storage dir to
www-data
? That is what the laravel docs recommend.
Oh, thanks for looking that up. Yeah, that makes sense to me.
🐛 Bug
I've seen this error a few times in prod since the last deployment:
🙋♀️ Proposed Solution
We probably need grant ownership or write permissions to the www-data user during the post-deploy script.
✅ Acceptance Criteria