> > Marcos, > Your proposal would be very useful for me as well. What is the status of this? I am using S3 as well, but on Amazon Elastic Beanstalk.
Stephen, Mezzanine rocks. There are definitely a few sticking points when deploying on Amazon EC2 / Elastic Beanstalk + S3, but most of them I have overcome. The biggest issue is the thumbnail template tag (Not for reasons that are your fault). For the sake of info, here is the issue: Amazon EB and EC2 uses an interesting app deployment mechanism. Each time you update your app it increments a number in a directory, deploys your app into that directory, and starts the server. For instance, if you go with out of the box Mezzanine settings your static and media content goes here: /opt/python/bundle/1/app/static/media On subsequent deploys the new deploy will go here: /opt/python/bundle/2/app/static/media Note the incremental number change. So, the first issue is that the uploaded media disappears with each deploy because it is IN the app directory. The solution was to use django storages with S3 (and help from s3_folder_storage). That fixes the issue for uploading media and not have it be erased across deploys. If you didn't use S3, you could write your own script that runs on each deploy and copies over previous uploaded images. No fun and quite a patch. So that leads me to the final problem. Thumbnails does not work with S3 (you already know this). I understand the issue, but is there any other workaround? I suppose I could monkey patch the tag to do something completely different and upload the thumbnail to S3. Any thoughts on the issue? -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
