Figure out deployment

[seanmonstar]

@gene1wood since we only need static content, can we get setup to easily deploy changes this week?

[gene1wood]

Depends on what servers we'd want this hosted on. Also depends on the domain name that you're looking to host on. Is it "persona.org" or "www.persona.org"? I ask because the technical solutions for these 2 will be very different.

I'd probably need to base my work off of what was done for personastatus.org

[seanmonstar]

I imagine persona.org, but I can ask about www. If we did go with www, we'd still want persona.org to redirect to www.

[gene1wood]

Redirecting from persona.org to www.persona.org would be easy and a good way to go. Ya do find out if we can host this content at www.persona.org

[seanmonstar]

@r0bl0rd does living at www.persona.org and letting persona.org redirect to it seem reasonable?

[r0bl0rd]

Maybe short-term. 'www' is obsolete.

@seanmonstar Also, "static only" meaning not node/express w/ templates, CSS pre-processor, etc? Why not do everything as a modern web app?

[seanmonstar]

Another reference point: mozilla.org redirects to www.mozilla.org.

We don't yet gain anything by using node to serve the content. Not using it makes for much easier deployments, such as we wouldn't even need to bother Gene, we could just push to a branch. We can still use a "build" script to compress everything.

When a dynamic backend is needed, simple enough to take the HTML and turn them into templates.

[gene1wood]

@r0bl0rd When you said "'www' is obsolete" it got me thinking. I hadn't heard of this before. Upon googling about it, the religious war going on out there about www vs no-www surfaced. "'www' is obsolete" is probably not so much a state or objective fact, more a viewpoint. I was curious if that was indeed the standard out there and it looks like it may not be. I polled the Alexa top 500 and it looks like about 76% of sites redirect from http://example.com/ to http://www.example.com/

So I'd say at the very least we're safe and in good company redirecting from http://persona.org/ to www or login

[ozten]

My understanding, is that it is much more expensive to scale persona.org versus developers.persona.org (or www or whatever), because of load balancing.

Can we put a business requirement and $$$ cutoff where that requirement isn't valid anymore?

[seanmonstar]

@gene1wood hows deployment to production looking? We've been staging using gh-pages and http://anosrep.seanmonstar.com. @r0bl0rd feels that it's so much better than current, that we should get it live ASAP. The hope is we can push text and graphics tweaks as we think of them.

I've since written a script in scripts/deploy.js that will build the static files, checkout a target branch, and push the re-built site up to Github. Can we use post-commit to deploy?

[seanmonstar]

@gene1wood bump :)

[gene1wood]

@seanmonstar I hadn't realized this was waiting on me. I've not yet put any work into spinning up servers to host this or putting together provisioning.

How about this : To get this going quickly let's not do on-demand code pushing and instead something like a nightly code pull. Can you provide the git URI of this repo your referring to as what deploy.js creates?

[ozten]

Did we do a kick off meeting across disciplines so everyone knows what's coming and who is doing what?

[seanmonstar]

@gene1wood it works like node ./scripts/deploy.js <branch-name>. So, I can push to the prod branch...

I think that'd be https://github.com/mozilla/persona.org/tree/prod ?

[gene1wood]

@seanmonstar No luck on that git URI. Can you point me to where it is on the web and I can deduce the git URI?

[gene1wood]

@ozten We did not (to my knowledge)

[seanmonstar]

@gene1wood sorry, I hadn't actually pushed there yet. I just did.

[gene1wood]

@seanmonstar got it git clone https://github.com/mozilla/persona.org -b prod

[seanmonstar]

@gene1wood so whatcha think?

[r0bl0rd]

Fair enough. I don't see how 'www' adds user value, thus the reasoning 'www' is at best superfluous.

Random notable dubdubdub obstainers: http://jquery.org/ http://github.com/

On Aug 20, 2013, at 1:01 PM, Gene Wood notifications@github.com wrote:

@r0bl0rd When you said "'www' is obsolete" it got me thinking. I hadn't heard of this before. Upon googling about it, the religious war going on out there about www vs no-www surfaced. "'www' is obsolete" is probably not so much a state or objective fact, more a viewpoint. I was curious if that was indeed the standard out there and it looks like it may not be. I polled the Alexa top 500 and it looks like about 76% of sites redirect from http://example.com/ to http://www.example.com/

So I'd say at the very least we're safe and in good company redirecting from http://persona.org/ to www or login

— Reply to this email directly or view it on GitHub.

[seanmonstar]

@gene1wood status?

[gene1wood]

@seanmonstar Worked on this at the end of last week and have been testing ( https://github.com/mozilla/identity-ops/commit/4bfe7d1d92115d2c2fd23f44d635aba878155004 ). Been delayed by firefighting this week.

[seanmonstar]

Yea, darn those fires. Thanks.

[gene1wood]

Deployment logic completed and deployed. You can see the site at https://www.persona.org/

https://github.com/mozilla/identity-ops/commit/56e713bfc641f87c8ac344deb66b0059b51a462e
https://github.com/mozilla/identity-ops/commit/6e71e0418d57f666af7110afa44572dcedeb4ce3

I ended up hosting this on our rootzone servers

[gene1wood]

@seanmonstar I'll leave it to you to announce this to dev-identity and/or @MozillaPersona on twitter as it's your baby =)

[seanmonstar]

\o/

/cc @r0bl0rd @ryanfeeley