Old question, but I figured it's worth answering.
In your settings file you have to set the Root URL configuration file.
Right now it looks like this:
ROOT_URLCONF = %s.urls % PROJECT_DIRNAME
Change it to this:
ROOT_URLCONF = urls
Because Elastic Beanstalk doesn't use the project name as the
.amazonaws.com/bucket_name'*
*S3_URL = 'https://s3.amazonaws.com/bucket_name
https://s3.amazonaws.com/bucket_name'*
*MEDIA_URL = S3_URL*
*STATIC_URL = S3_URL*
On Friday, May 23, 2014 2:36:24 PM UTC-4, Brad Bode wrote:
Although you are having a slightly different issue you might want to
join
Well when the time comes I will ask for help. When I take point on this it
will happen fast though and I will likely do it all myself and let the
community improve it from there. I know for a fact that I will need a more
app like feel and DRF + Mezzanine + Angular JS is my choice. However, I do
1) Why do you define
AWS_SECRET_KEY = os.environ['AWS_SECRET_KEY']
AWS_SECRET_ACCESS_KEY = AWS_SECRET_KEY
and not just
AWS_SECRET_ACCESS_KEY = os.environ['AWS_SECRET_KEY']
Legacy testing crap code basically (a poor understanding of settings). I
updated the settings to remove
If your desire is to store thumbnails on S3 then the easiest solution I
found is to replace the thumbnails generator that mezzanine provides. Why?
As good as mezzanine is it is not setup for S3 bucket storage of thumbnails
and will only generate them with the roo media url.
What do you do?
Mezzanine is humming along on AWS with a load balancer, ssl, RDS, etc...
I've learned a lot, but now I am hoping someone has the answer here.
For whatever reason the asset_proxy is using HTTP not HTTPS. The problem
ONLY seems to occur when I click on the HTML editor in a rich text page.
The
Solved... for now. Although I wouldn't call it a bug I got the most help
out of this bug listing : https://github.com/stephenmcd/mezzanine/issues/530
So the solution for me was two fold. First, I had to make sure all usages
of the mezzanine thumbnail tag would work. Ideally this would be done
are changed?
Cheers,
M
On Mon, Apr 21, 2014 at 2:41 AM, Brad Bode for...@gmail.com javascript:
wrote:
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
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
