Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hey @enr9! 👋
The error "Disk named spaces cannot be accessed" could be caused by a couple of different issues.
Your config/filesystems.php configuration looks good, but make sure that the 'spaces' disk is set as the default or explicitly used in your code. Check your config/filesystems.php file for the default disk setting:
'default' => env('FILESYSTEM_DISK', 'spaces'),
If you’re not using 'spaces' as the default, make sure you are specifying the 'spaces' disk when working with files in your code:
Storage::disk('spaces')->put('file.txt', 'Contents');
On another note, double-check your bucket name in your .env file:
DO_SPACES_BUCKET=your-bucket-name
It should exactly match the name of your Spaces bucket in DigitalOcean. Sometimes, small typos or extra spaces can cause issues.
For DO_SPACES_ENDPOINT, it’s best to use the HTTPS endpoint to ensure secure connections:
DO_SPACES_ENDPOINT=https://fra1.digitaloceanspaces.com
If you don’t have the https:// prefix it might cause weird problems.
Also sometimes, changes to the .env file or configuration files might not take effect due to caching. Clear your configuration cache using:
php artisan config:clear
Let me know if the problem persists!
- Bobby