Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hey everyone, I've moved a project of mine entirely to Laravel Cloud, everything works like a charm with 0-setup-head. But today I ve seen a huge problem, I already had lots of images in there (with filament panel if it helps), today I had to change a thing on the panel and triggered the auto-deploy. When I opened again the panel after deployment, none of the images appeared, tried to clear config (config:clear), link storage, none of this options works, the images just disappeared.
What are the recommended solution? I've seen that there's image buckets in there but I thought there were an internal storage from cloud itself, also adding a image bucket wouldn't be very cool since I would need to change lots of things on the panel (using public disk locally vs r2 in production).
Open for your suggestions, thanks in advance.
@rodrigofplourenco As the name suggests, Laravel Cloud is cloud-based. That means storage is not going to persistent. You need to store your files and images somewhere else (such as S3), just like you would if you were using another cloud hosting platform like Heroku.
Docs: https://cloud.laravel.com/docs/resources/object-storage
@martinbean Thanks for the response, it's the first time using Cloud Solutions (always used classic-old Ubuntu VPS Setup). I will set up object storage and use it, what would be the solution for local development? There is any way to set disk storage to public on filament (local dev) and to r2 to production? Without changing every single thing manually?
@martinbean Nvm, easier than I thought it would be, only needed to install the required package and use Storage::url instead of asset function and Laravel cloud's generated .env take care of the rest, awesome! Thanks for your help Martin!
Please or to participate in this conversation.