Take care: Work In Progress here. This article might be incomplete or contain errors. Know something we don't? Help us! Contribute here on GitHub

Manage Craft assets

Learn how to deploy Craft CMS runtime data to the Object Storage with fortrabbit Professional Apps.

Get ready

For best results here, make sure you have completed all steps from the get ready guide and have Craft running on your local machine, setup and deployed. This guide is for advanced users on the advanced Pro Stack.

About Craft CMS assets

With Craft 3, the "assets" folder contains files that are managed by the CMS. This is the user generated stuff, uploaded files, mostly images — also see the official Craft docs on that.

The fortrabbit Craft CMS starter .gitignore file excludes /web/assets/* from Git. Why? Because, code and content are separated and the assets uploaded to an Pro App will get destroyed the next you time deploy anyways, see here for more and why.

Upload assets to the Object Storage

So what you want: is to swap the assets folder on the file system with external files stored on the fortrabbit Object Storage. We have developed a Craft plugin to connect the fortrabbit Craft App with the Object Storage. All uploads will transferred to the Object Storage directly, all URLs will point to the Object Storage. See the install guide on GitHub for usage:

Once the plugin is installed and enabled, a new Volume Type "fortrabbit Object Storage" is available. In your config/volumes.php you can setup additional volumes.

To access the Object Storage from your computer, use a S3 compatible SFTP client - Transmit for Mac works best in our experience.

Next steps

Continue with tuning Craft.

Further readings

Craft CMS

Install guides

Develop & deploy




Need individual help?
Learn about Company plans ›
Looking for an old article?
See the full list of articles ›
Found an error?
Contribute on GitHub ›