file-storage

Configure file storage providers by selecting Disk, S3, Azure Blob, or Cloudinary backends and wiring their credentials into appsettings. You register storage services through Spiderly's builder to enable seamless blob upload behavior and DI integration.

Spiderly supports declaring blob-related attributes with required MIME type whitelists and size constraints. You apply these validation rules to your entities to enforce consistent file handling and restrict uploads to approved formats.

Yes, Spiderly works with Azure Blob, S3 Public, S3 Private, Cloudinary, and Disk backends. You can choose your preferred storage provider during configuration to manage file references and blob upload behavior across different environments.

The best way to manage blob cleanup is using Spiderly's multi-step upload lifecycle, which handles automatic cleanup of non-active blobs and editor images. This lifecycle management enforces consistent configuration and removes orphaned files safely.

File uploads fail during DI registration when storage services are not properly wired into Spiderly's builder or appsettings lack correct credentials and endpoints. Troubleshooting workflows verify naming conventions, validation rules, and provider configuration to resolve errors.

Yes, you can apply consistent naming prefixes and folder structures to ease maintenance. Spiderly enforces clear naming conventions during the upload flow, ensuring organized file references across your selected storage backend.