1113276 - Environments for public browsing

Status: RESOLVED FIXED

(Websites :: Shape of the Web, defect)

Description

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

We will need an ongoing public space to host WIP Shape of the Web builds for

1. Show proposed content changes in context to stakeholders.
2. Allowing the community a low-overhead avenue of trouble-shooting the site.

Very much like a demo server for bedrock, but something that is always up.

Comment 1

[Osmose [:osmose, :mkelly]]

While we wait on IT to set up S3 for a dev server, I've got the site running on my own subdomain via Github Pages: http://lorax.mkelly.me/

Will be submitting a pull request soon with a grunt task for updating Github pages. Anyone with commit access to the repo will be able to update. :D

Comment 2

[[github robot]]

Commits pushed to master at https://github.com/mozilla/lorax

https://github.com/mozilla/lorax/commit/f0557e5709d66d8f38016a9e64a00905c3591291
Bug 1113276: Add grunt command to deploy to gh-pages.

Just run `grunt build gh-pages`!

https://github.com/mozilla/lorax/commit/63c71cf237860b5dd549fc7ef9421a38286420b8
Merge pull request #7 from Osmose/deploy-gh-pages

Bug 1113276: Add grunt command to deploy to gh-pages.

Comment 3

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

Having trouble direct linking to pages.

E.g. http://lorax.mkelly.me/checklist

But if I go to the home page first, then click on "Checklist" it is okay

Comment 4

[Osmose [:osmose, :mkelly]]

(In reply to Cory Price [:ckprice] from comment #3)
> Having trouble direct linking to pages.
> 
> E.g. http://lorax.mkelly.me/checklist
> 
> But if I go to the home page first, then click on "Checklist" it is okay

Github pages limitation. Will not apply once we have a proper dev environment.

Comment 5

[Osmose [:osmose, :mkelly]]

Actually I could make a custom 404 page just for Github pages but it seems unnecessary when we're going to drop it anyway.

Comment 6

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

(In reply to Michael Kelly [:mkelly,:Osmose] from comment #5)
> it seems unnecessary when we're going to drop it anyway.
Agreed, thanks.

Comment 7

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

The agency also delivered an "intro" page (http://lorax.work.co/intro), but I don't see it on the GH page.

Comment 8

[Osmose [:osmose, :mkelly]]

(In reply to Cory Price [:ckprice] from comment #7)
> The agency also delivered an "intro" page (http://lorax.work.co/intro), but
> I don't see it on the GH page.

Just thought up a workaround that takes advantage of Angular automagically converting anchors to pushstate URLS: http://lorax.mkelly.me/#intro

Seems to work!

Comment 9

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

:pmac - with bug 1113371 closed, please move forward with pushing mozilla/lorax to the AWS instance. API keys sent privately.

Comment 10

[Paul [:pmac] McLanahan]

I've got a proof of concept pushed to a personal s3 bucket using grunt-s3:

http://pmac-lorax-test.s3-website-us-east-1.amazonaws.com/

Now I'm going to add travis to the repo and use it to auto-deploy to the real bucket when new commits hit master. This way we can control who can push to prod via github access instead of passing AWS keys around.

Comment 11

[[github robot]]

Commit pushed to master at https://github.com/mozilla/lorax

https://github.com/mozilla/lorax/commit/eb9fc946d83656afda20bc13b9bd1ed6434500ba
Fix bug 1113276: Add s3 deployment via grunt-s3 and Travis-CI

Comment 12

[Paul [:pmac] McLanahan]

Travis autodeploy has succeeded!

http://lorax.s3-website-us-west-2.amazonaws.com/

It's not working because the old json has been deleted from the lorax repo and the site isn't yet pointed to the data on bedrock. I also need access to the admin console for the bucket to set the error document to index.html so the deep link urls will work.

Comment 13

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

(In reply to Paul McLanahan [:pmac] from comment #12)
> Travis autodeploy has succeeded!
> 
> http://lorax.s3-website-us-west-2.amazonaws.com/
> 
> It's not working because the old json has been deleted from the lorax repo
> and the site isn't yet pointed to the data on bedrock. I also need access to
> the admin console for the bucket to set the error document to index.html so
> the deep link urls will work.
Hi :digi - in bug 1113371, you helped us set up an AWS instance. Is it possible to gain access to the console?

Comment 14

[Brian Hourigan [:digi]]

> Hi :digi - in bug 1113371, you helped us set up an AWS instance. Is it
> possible to gain access to the console?

Hi Cory!

My apologies, I was drown in some large projects in Q1 and did not pay attention to bugmail for a long time. I don't think console access is a problem. Since quite some time has passed, could you please confirm that it would still be helpful to you?

Comment 15

[Cory Price [:ckprice] (bugmail disabled, NI me!)]

(In reply to Brian Hourigan [:digi] from comment #14)
> > Hi :digi - in bug 1113371, you helped us set up an AWS instance. Is it
> > possible to gain access to the console?
> 
> Hi Cory!
> 
> My apologies, I was drown in some large projects in Q1 and did not pay
> attention to bugmail for a long time. I don't think console access is a
> problem. Since quite some time has passed, could you please confirm that it
> would still be helpful to you?

I believe we are working through this in bug 1154326. Thanks!