Skip to main content
Choose a private local disk or S3 disk, then configure queues and scheduled maintenance for your enabled features.

Run only the workers you configure

Use Laravel’s normal scheduler and queue worker service. Route each optional worker to its configured connection and queue. Keep the timeout and retry settings consistent with the longest supported job in that queue.
These worker examples assume a configured Redis connection and matching feature settings. For video edits, thumbnails, assistant runs, and workspace operations, use the actual queue names in the published configuration. Check the Laravel worker process after deploying configuration or code changes.

Validate delivery and recovery

  1. Test a signed-in user and an unauthorized user against the same workspace and asset.
  2. Upload a small image and an allowed large file. Verify the original, progress, and derivative states independently.
  3. Preview a document and seek within a video through the same ingress and CDN used in production.
  4. Create and disable a test share. Reopen its URL in a separate session to verify revocation.
  5. Verify a restore from the application’s backup process with the database, private objects and required encryption keys in the same recovery exercise.
See encryption for key handling and existing-object migration. Keep Studio environment values, API tokens and provider credentials out of public logs and browser bundles.