Closed
Bug 1192284
Opened 10 years ago
Closed 10 years ago
Run popcorn js static site in S3 with cloudfront on HTTPS
Categories
(Webtools Graveyard :: Air Mozilla, defect)
Webtools Graveyard
Air Mozilla
Tracking
(firefox42 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox42 | --- | affected |
People
(Reporter: peterbe, Assigned: jschneider)
References
Details
Currently, the whole of the static assets plus HTML lives inside the airmozilla repo: https://github.com/mozilla/airmozilla/tree/master/airmozilla/popcorn/static/popcorn/PopcornEditor
All of this can sit on its own repo and hosted separately on S3.
Ideally we'd love a travis job that automatically builds to S3 on successful completions. (no tests available yet)
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → chris.lonnen
Comment 1•10 years ago
|
||
I've created the necessary buckets and creds. Can one of you break out the necessaries into their own repo with travis-ci running and required build steps? I'll open a PR against that to include the 'publish to s3' bits.
Also -- what domain should this live at, and does it need ssl?
Reporter | ||
Comment 2•10 years ago
|
||
We chatted about this but for completeness I'll answer here:
* The repo is github.com/mozilla/PopcornEditor
* No current .travis.yml file
* The domain name doesn't matter. HTTPS does. Something like https://abc123.cloudfront.aws.com/editor.html is fine.
Reporter | ||
Comment 3•10 years ago
|
||
Correction!! The repo is https://github.com/mozilla/popcorn-editor
Comment 4•10 years ago
|
||
It lives!
http://org.mozilla.air.popcorneditor.s3-website-us-east-1.amazonaws.com/
I have it running in S3. Did you want it wrapped in CloudFront?
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Chris Lonnen :lonnen from comment #4)
> It lives!
>
Hurray!
So every git push to origin/master will build to that bucket?
> http://org.mozilla.air.popcorneditor.s3-website-us-east-1.amazonaws.com/
>
> I have it running in S3. Did you want it wrapped in CloudFront?
Well, performance isn't that important since the amount of traffic will be scares. However, HTTPS is a must.
Assignee | ||
Updated•10 years ago
|
Assignee: chris.lonnen → jschneider
Assignee | ||
Comment 6•10 years ago
|
||
What is the DNS for this page going to be?
Reporter | ||
Comment 7•10 years ago
|
||
(In reply to JP Schneider [:jp] from comment #6)
> What is the DNS for this page going to be?
Happy to just use a cloudfronty URL.
Reporter | ||
Comment 8•10 years ago
|
||
e.g osudhfiowuehcvwc.cloudfront.net
Assignee | ||
Comment 9•10 years ago
|
||
CDN is all created, it's currently populating.
d2edlhmcxlovf.cloudfront.net will be the url
Reporter | ||
Comment 10•10 years ago
|
||
https://d2edlhmcxlovf.cloudfront.net/PopcornEditor/editor.html works and that's what matters.
It's a bit strange that unknown URLs cause a 403 Forbidden instead of a 404 Not Found (e.g. https://d2edlhmcxlovf.cloudfront.net/doesnotexist)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 11•10 years ago
|
||
The public does not have list permissions, so it sees it as a 403 instead of a 404. I can flip that bit on if you want.
Reporter | ||
Comment 12•10 years ago
|
||
(In reply to JP Schneider [:jp] from comment #11)
> The public does not have list permissions, so it sees it as a 403 instead of
> a 404. I can flip that bit on if you want.
Please do.
Updated•4 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•