Hello! We are currently managing a project that involves such a large volume of media data that our available storage space won’t be sufficient. Does anyone have experience with what Omeka S requires if we were to store the media externally – that is, not in the “files” directory on the webspace? We would be very grateful for any help or feedback!
Best regards,
Emma
Hello Emma,
You can use AnyCloud module which allows you to store your data externally.
Best regards,
Thibaud
Hi Emma,
We store all our media in Amazon S3 rather than the local files directory, using the AmazonS3 module by Daniel-KM. It swaps out Omeka’s file store, so originals and derivatives go straight to your bucket with no other changes needed.
You’ll need an AWS Account and create an S3 bucket plus an access key with read/write permission, entered in the module’s settings in the admin. We also put CloudFront in front of the bucket and set the module’s CloudFront URL option so the site serves media from the CDN.
One caveat: the module keeps the bucket name and credentials in the Omeka database, so sanitize those settings if you ever copy your production DB to a test install.
As mentioned above, Any Cloud is also a good choice, especially if you want a provider other than AWS (Dropbox, Google Cloud, Azure, etc.). Just note it doesn’t support migrating between providers later, so pick one and stick with it.
Good luck!