You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Home » Issues » Feature request #1230

Feature request #1230: Move static assets onto Amazon S3

The idea is to move static assets onto another domain, say the rails subdomain, and leave the main site on wincent.dev.

In this way the wincent.dev cookie won't be sent when requesting the assets, so they should load faster.

Both domains have an SSL cert, so there should be no problems there.

Greg Hurrell 2009-02-16T12:50:37Z
Status changed:
- From: New
- To: Open
Greg Hurrell 2009-04-17T08:42:21Z

I currently have three domains with SSL certs: wincent.dev, the rails subdomain, and one other.

For the time being I don't want to touch wincent.dev at all because it's handled by Apache and that set-up must remain intact until all of the old (Apache-served) parts of the site are brought over here (and even then will probably want to wait quite a while to give Google and friends time to index the new content instead).

Not sure if I want to keep renewing the SSL certificate for the rails subdomain forever, so that may not be the best long term choice either. At least in the short term, it should be ok.

Long term I probably want a new subdomain, like assets.example.com.
Greg Hurrell 2010-06-24T09:11:59Z

Another option to consider here is moving some assets to Amazon S3. Seeing as I have to use HTTPS, and seeing as EC2 instances can only have 1 external IP address, I can't run multiple HTTPS sites off the same instance (each would need a different IP), the only choice is moving the assets onto another instance, and if I'm going to do that I may as well move them to S3.

Still not sure if it's actually worth it. Probably shelve the idea until performance becomes a problem, and it probably never will.
Greg Hurrell 2010-06-24T09:12:11Z
Summary changed:
- From: Move static assets onto different domain
- To: Move static assets onto Amazon S3

Comments are now closed for this issue.

Menu