Switching our file storage to Amazon S3 will aid in achieveing T26, but will also give us more flexibility. Amazon S3 is also pretty much a lot faster than storing them locally. This means that both sitemaps and images can be served through S3, and also database dumps.
Description
Description
Revisions and Commits
Revisions and Commits
| Unknown Object (Diffusion Commit) | |
| Unknown Object (Diffusion Commit) |
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | OriginalAuthority | T26 Distribute traffic over different servers | ||
| Resolved | OriginalAuthority | T27 Switch file storage to Amazon S3 |
Event Timeline
Comment Actions
I've managed to set up the bucket, and it correctly handles uploads and deletions. There does appear to be an issue with accessing files, however, when using a custom URL. I'll keep investigating, but it shouldn't be too long until this can be marked as compelete.
Comment Actions
The back-end of this is largely done. All that remains is to turn off uploads temporarily and move the files across to the bucket. Afterwards, wikis will need to change their URLs in ManageWiki for logos or anything else like that because they will be served via static.telepedia.net rather than {$wgDBname}.telepedia.net/images/{$wgDBname}.