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)
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?
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.
Correction!! The repo is https://github.com/mozilla/popcorn-editor
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?
(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.
What is the DNS for this page going to be?
(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.
CDN is all created, it's currently populating. d2edlhmcxlovf.cloudfront.net will be the url
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
Last Resolved: 3 years ago
Resolution: --- → FIXED
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.
(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.
You need to log in before you can comment on or make changes to this bug.