We go a different route for that - we just use a regular page where one
can upload a file and just create a node with a reference to the file
but store the file somewhere on the file system where it can be directly
served from apache.
Ruben
Joshua Portway wrote:
Has anyone tried to set up a system whereby the DMS uses Amazon S3 to
store and serve files?
I have a site that currently uses Magnolia for managing most of it,
but has quite a lot of movie content - the movie files are up to 600mb
in size, and need to stream smoothly, hence I currently use Amazon S3
storage + Cloudfront content delivery network. The solution works
pretty well, but the problem is that there's no way to manage the
movie files from within Magnolia, which makes uploading and changing
movies complex, time consuming and error prone.
Is there any way to change the back end file system used by the DMS to
use S3 (or something similar)?
My idea would be that the DMS would keep metadata about files in the
database, but actually store the files on S3 (perhaps with a local
master copy too, just so that everything is in one place for
migrations etc). When a file was requested it would return the S3 URL
for the file so it would be served directly from Amazon through their
content delivery network.
Josh
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
