search

caylan / Bulletin

Keep everyone in the loop.
5 stars 2 forks source link

Serving Static Resources #22

Closed awdavies closed 11 years ago

awdavies commented 12 years ago

As of current, we have no way to send static resources. We're running in debug mode, which serves all static resources locally. When we get to production, we'll need a way to securely send static resources to the web-page independent of our own web app.

This can likely be done with any conventional web server (like Apache, for example).

go4ble commented 12 years ago

i'm thinking about setting up an aws CloudFront for this. it's pretty cheap, $0.12 for the first 10TB, and the $0.08 for the next 40TB. When you get to the PB, it's only like $0.02 for each 5PB. .. and, i still have around $60 left in credits for aws from 344 :)

go4ble commented 11 years ago

All static files have been uploaded to AWS S3 and distributed via CloudFront.

In the settings file, I've changed STATIC_URL to point to 'http://cloudfront.bulletinapp.net/'

From now on, in the templates, reference a static file using {{ STATIC_URL }} e.g.

I am now going to work on getting everyone access to the S3 bucket holding the site content