Uploading Settings

Choose where new public uploads are stored and set up Local Disk, Amazon S3, or Wasabi without breaking existing media.

Uploading settings page in TruCMS

Uploading settings choose where public media and uploaded files are stored.

What Public Uploads Disk changes

The Public Uploads Disk controls where new public media/files are stored. The available choices are Local Disk, Amazon S3, and Wasabi. This affects media used across the CMS and enabled modules, so choose the storage location before importing a large media library.

Changing the disk does not move existing files

Switching from Local Disk to S3/Wasabi (or back again) changes where new uploads go. Existing media can still refer to the disk where it was originally stored. Do not delete or disconnect the old storage until those existing files have been migrated or you have confirmed they are no longer needed.

Choosing a storage option

OptionBest fitWhat you need
Local Disk (default)Most single-server/shared-hosting installations.Writable application storage and a working public storage link.
Amazon S3Sites that want object storage separated from the web server or use AWS infrastructure.S3 bucket, region, access key and secret with access to the bucket.
WasabiSites using Wasabi's S3-compatible object storage.Wasabi endpoint, region, bucket, access key and secret.

Set up Local Disk

Local Disk stores public files on the same server as TruCMS. It has no external service cost and is normally the easiest option, but the server is responsible for both the website and the media files.

  1. Open Settings → Uploading and select Local Disk (default).
  2. Save changes.
  3. Upload a harmless test image through a normal media/content screen and confirm it displays on the frontend.

If uploaded files exist but cannot be reached publicly, open Settings → Advanced and use Link Storage to repair the public storage link, then test the file again.

Back up uploaded media

A website backup should include both the database and local uploaded files. Database-only backups do not protect images/documents stored on Local Disk.

Set up Amazon S3

Create the S3 bucket before changing TruCMS. Use credentials with the minimum permissions needed to create, read and manage the objects TruCMS stores in that bucket.

Amazon S3 upload configuration in TruCMS with credentials hidden

Amazon S3 requires a bucket, region and credentials with suitable access to that bucket.

  1. In AWS, create or choose the S3 bucket and note its exact region.
  2. Create credentials that can access that bucket. Do not use a personal/root AWS credential for routine website storage.
  3. Open Settings → Uploading and select Amazon S3.
  4. Enter Amazon S3 Key, Amazon S3 Secret, Amazon S3 Region and Amazon S3 Bucket.
  5. Save changes. TruCMS validates the bucket connection when the bucket setting is saved.
  6. Upload a new test image/file and confirm it can be displayed from a public page.

Amazon S3 and Amazon SQS share AWS key/secret/region settings

If Amazon SQS is also used for the Queue Driver, changing the AWS access key, secret or default region here also affects the SQS configuration. Use credentials that are appropriate for both services or coordinate the change with your server administrator.

Set up Wasabi

Wasabi uses an S3-compatible API but needs its own endpoint and credentials.

Wasabi upload configuration in TruCMS with credentials hidden

Wasabi uses an S3-compatible connection with its own endpoint, region, bucket and credentials.

  1. Create or choose a Wasabi bucket and note its region and endpoint.
  2. Create an access key/secret permitted to use that bucket.
  3. Open Settings → Uploading, choose Wasabi, and enter Wasabi Endpoint, Wasabi Key, Wasabi Secret, Wasabi Region and Wasabi Bucket.
  4. Save changes. The bucket setting is connection-validated.
  5. Upload a test file and confirm it displays correctly from the public site.

Moving an existing site to remote storage

Do not treat the disk selector as a migration tool. For an established site, use this order:

  1. Create a full backup of the database and existing uploads.
  2. Prepare the new S3/Wasabi bucket and credentials.
  3. Copy/migrate existing media using a migration method appropriate to your hosting/storage plan.
  4. Change Public Uploads Disk and test new uploads.
  5. Visit representative old pages, products and services to confirm existing media still loads.
  6. Only remove the previous storage after the migration and verification are complete.

Troubleshooting uploads