Closed Bug 912694 Opened 11 years ago Closed 11 years ago

set up a cdn.webmaker.org for officially sanctioned ext. libraries

Categories

(Webmaker Graveyard :: DevOps, defect)

Product:
Webmaker Graveyard
Component:
DevOps
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: michiel, Assigned: johns)

Details

(Whiteboard: mozfest)

In order to offer users some easily available webmaker-sanctioned libaries, it would be nice to set up a cdn.webmaker.org and use it to host our product libraries, like popcorn.js, maybe a domdiff.js, processing.js etc.
Amen to this. Moving to DevOps, as I suspect that's what this needs.
Component: Thimble → DevOps
Whiteboard: mozfest
Can we use cloudfront for this? We don't need a CDN sitting in front of anything, so from my view, that would be the way to go.
Yep, cloudfront is fine for JS. You'll need to add an SSL cert though, since you can't load http scripts in https.
Ugh, that will be $600 a month. Everyone OK with that? I can setup the bucket and distro today
Flags: needinfo?(brett)
I'd prefer not to pay $600/month. What does that mean in terms of available URLs / options?
Flags: needinfo?(brett)
Assignee: nobody → johns
Flags: needinfo?(johns)
So I suppose the big question is: Why do you want a CDN? We can just use S3 if we want, and then proxy it like we do with makes.org. this causes a 10X slowdown in downloads, but it does not cost $600 a month.
Flags: needinfo?(brett)
Flags: needinfo?(johns)
I've setup a bucket, assets.webmaker.org, and a cloudfront distro. https://d37xx2sul3y8g2.cloudfront.net Who all needs to be able to upload to this bucket?
I'd say myself, humph, jbuck and pomax for now.
Flags: needinfo?(brett)
Whiteboard: mozfest
oops. I had removed mozfest, but this seems close enough we should let it ride!
Whiteboard: mozfest
jp, can we move on this, and have some more friendly URLs?
Flags: needinfo?(johns)
JP finished this off, with https://d37xx2sul3y8g2.cloudfront.net setup. If it must be a friendly URL, then we'll have to pony up $600/month for a custom SSL certificate or go with the slower and cheaper option of an SSL proxy.
Ah, awesome. So how do we upload there?
JP, could you send credentials for this and then we can mark as resolved?
This should now be done! Let me know if anyone else gets jammed up.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(johns)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.