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, set up and deployed. This guide is for advanced users on the advanced Pro Stack.

Craft CMS assets on Pro Apps

By default assets are stored in a local volume, which means user uploads are located in a folder along with the code. With Pro Apps you separate the uploads from your code, since your App usually runs on multiple nodes which do not share the same file system. Every time you deploy a new version of Craft or change templates, we replace the old with the new state. Read more about the nature of ephemeral storage here.

Upload assets to the Object Storage

First, make sure to have the Object Storage Component enabled with your Pro App. That gives you access to our S3 compatible Object Storage. You don't need an AWS account, since this is a first party service we provide. Learn more about the fortrabbit Object Storage here.

To connect Craft CMS with the Object Storage, install the fortrabbit/craft-object-storage plugin. On the GitHub page of the plugin you will find further setup instructions. As usual we expect this to be done locally first and then deployed via a git push.

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

Accessing the Object Storage from your computer

See the main Object Storage article for more details on how to access the Object Storage from your computer.

Next steps

Continue with tuning Craft.

Further reading

Craft CMS

Install guides

Code access













The Dashboard


Tips & tricks




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